This is the mail archive of the
mailing list for the Cygwin project.
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin-apps at cygwin dot com
- Date: Sun, 04 May 2014 00:51:37 -0500
- Subject: Re: perl-5.18.2-1
- Authentication-results: sourceware.org; auth=none
- References: <534078A2 dot 4000601 at tiscali dot co dot uk> <87bnwf2cjl dot fsf at Rainer dot invalid> <534174C4 dot 5010608 at tiscali dot co dot uk> <87y4zi1kib dot fsf at Rainer dot invalid> <5341A3F5 dot 2040506 at tiscali dot co dot uk> <CAHiT=DF117Jf0jdV8KQHOakkOw3_A5FvmSRKRRVnXGt-MLY6cA at mail dot gmail dot com> <8761mlx7im dot fsf at Rainer dot invalid> <CAHiT=DFhajOOFDeFseptmrPVXHGVjrAiFxDaW6Z7qQ6XR070DQ at mail dot gmail dot com> <87a9bvsnse dot fsf at Rainer dot invalid> <CAHiT=DEe1O4Vn7dp2mPwUNvEagZDtauu9_ZS1vfpEgZ+V0wt4A at mail dot gmail dot com> <8761loegk8 dot fsf_-_ at Rainer dot invalid> <53644EFC dot 1090703 at cornell dot edu>
On 2014-05-02 21:05, Ken Brown wrote:
On 5/2/2014 4:21 AM, Achim Gratz wrote:
Reini Urban writes:
It's vastly easier to keep perl_vendor than to split it up.
I've been looking at the test package for the upcoming 5.18.2 release
announced in http://cygwin.com/ml/cygwin-announce/2014-04/msg00038.html
and I'd like to contest that assertion again.
TL;DR: I still propose to keep each Perl distribution as a separate
package (yes, I'm willing to ITP them) and move perl_vendor to an
umbrella package that simply bundles those individual packages plus
perhaps a README.
I'm not even sure that such an umbrella is needed. Maintainers of
packages that rely on Perl modules can simply use cygport to determine
which perl-* packages are required. I don't see the need for a
perl_vendor package that brings in some arbitrarily chosen collection of
Reini, I know you think it's more work to split up perl_vendor than to
keep it as is, but Achim has offered to do the work. And it would make
things much easier for those of us who maintain packages that require
Perl modules. With the current bundling, we have to check for each
required module whether or not it's included in perl_vendor. I just did
this for biber, and it's very tedious. I hope you'll reconsider.
+1, and I'm willing to help with some of the modules as well.