X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <4760A137.1000706@users.sourceforge.net> Date: Wed, 12 Dec 2007 21:04:23 -0600 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Stop turning CPAN modules into Cygwin packages References: <1ff86f510712120704w5f175db9md89d05d936d535ed@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Igor Peshansky wrote: > FWIW, some of these modules might be worth packaging as part of the Cygwin > Perl package (in vendor_perl), rather than as separate packages. Actually, I wish that we would NOT be doing this. Separate modules should be packaged separately, because otherwise, as we have it now: 1) updating a module requires repackaging (and redownloading, and reinstalling...) the entire perl; 2) alternatively, the modules just get neglected and go stale; 3) some modules have binary dependencies which the perl core does not have, e.g. XML-LibXML. IMO these should all be broken out. (Hint: as Eric just discovered, packaging perl modules is *really* easy with cygport. But then again, I'm biased.) Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYKE3piWmPGlmQSMRCGqeAKCptGBM4umH2lKU7Rr+a/lwwgmjNgCg+Bzq mDaZcZPr4QrW1AdmfrdJR+w= =AokL -----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/