X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 12 Dec 2007 10:46:08 -0500 (EST) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: "Jerry D. Hedden" cc: The Cygwin Mailing List Subject: Re: Stop turning CPAN modules into Cygwin packages In-Reply-To: <1ff86f510712120704w5f175db9md89d05d936d535ed@mail.gmail.com> Message-ID: References: <1ff86f510712120704w5f175db9md89d05d936d535ed AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, 12 Dec 2007, Jerry D. Hedden wrote: > Eric Blake wrote: > > A new package, perl-Error-0.17010-1, is now available for use. > > > > NEWS: > > ===== > > This is a new package, providing the Error module for perl. > > What is the point of making this a Cygwin package? There > are no Cygwin specific changes, and it it can be installed > directly from CPAN using: > cpan -i Error As I understand it, this is a prerequisite for "git", which is a Cygwin package. In fact, that's the only reason I see for making CPAN modules into Cygwin packages (the Cygwin-specific patches, as you've said yourself, should eventually be sent upstream). > This seems to be becoming a trend. So far there are 8 CPAN > modules that have been made into Cygwin packages. Only 3 > have Cygwin specific changes that would justify them being > made into package: > perl-Locale-gettext > perl-Tk > perl-libwin32 > > The other 5 have no Cygwin specific changes: > perl-Error > perl-ExtUtils-Depends > perl-ExtUtils-PkgConfig > perl-Module-Build > perl-Win32-GUI FWIW, some of these modules might be worth packaging as part of the Cygwin Perl package (in vendor_perl), rather than as separate packages. > This seems like a bad practice. Ok, let's take these points one-by-one. > It adds a maintenance burden on the Cygwin system (because the packages > will need to be updated when the modules are updated), Yes, but that's the choice of the volunteer maintainer. Eric packaged these because he maintains git, and it was the easiest way for him to make sure the target system contained the required modules. So, in effect, it *eased* his maintenance burden. > they needlessly take up storage on the Cygwin servers, Storage is cheap, and nobody has complained yet. > and turning them into Cygwin packages adds no value over obtaining the > modules directly from CPAN. Sure it does. For one, they could be added as dependencies of other packages (as you yourself agreed), and also they can be included on installation CDs, etc, which could be installed without internet connection (which is one reason to not request CPAN install in a postinstall script). > Just because you can turn a CPAN module into a Cygwin > package doesn't mean that you should unless there are Cygwin > specific changes that need to be made. Even then, a better > approach is to send the appropriate patches to the module's > maintainer so that they can be integrated into the code and > uploaded to CPAN. BTW, this problem must have been encountered (and, hopefully, solved) by other distros. How does the Debian git package handle this? I seem to recall that at least Red Hat Linux at some point had packages for some CPAN modules... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "That which is hateful to you, do not do to your neighbor. That is the whole Torah; the rest is commentary. Go and study it." -- Rabbi Hillel -- 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/