Message-ID: <47608DD7.10703@byu.net>
Date: Wed, 12 Dec 2007 18:41:43 -0700
From: Eric Blake <ebb9@byu.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Stop turning CPAN modules into Cygwin packages
References: <1ff86f510712120704w5f175db9md89d05d936d535ed@mail.gmail.com> 	 <Pine.GSO.4.63.0712121036130.24563@access1.cims.nyu.edu> <6910a60712121732y28d1dccekddca0d14ad2b6f3a@mail.gmail.com>
In-Reply-To: <6910a60712121732y28d1dccekddca0d14ad2b6f3a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Reini Urban on 12/12/2007 6:32 PM:
> I hope Eric put it into vendor_perl, so there will no conflict when
> doing cpan -i Error
> Otherwise it's ok for me if some minor perl module is an external
> dependency.

Yes - cygport automatically puts perl modules into vendor_perl.

> 
>>From what I know by hard, Module::Build will be included in the next perl CORE
> package, and the others could go into vendor. Besides libwin32 and
> Win32::GUI of course.

At which point I would retire perl-Module-Build as obsolete.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHYI3X84KuGfSFAYARAsq2AJ9utMj4A4AEV6Iadg8BpSLuSeOsewCeOsHh
J6H/wqM5BRyOKHB42BvZNEg=
=Wbv4
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/