From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: perl-5.18.2-1
Date: Sat, 03 May 2014 02:06:00 -0000 [thread overview]
Message-ID: <53644EFC.1090703@cornell.edu> (raw)
In-Reply-To: <8761loegk8.fsf_-_@Rainer.invalid>
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)
+1
> 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
Perl modules.
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.
Ken
next prev parent reply other threads:[~2014-05-03 2:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 21:42 64-bit: Missing perl modules David Stacey
2014-04-06 6:32 ` Achim Gratz
2014-04-06 15:37 ` David Stacey
2014-04-06 16:38 ` Achim Gratz
2014-04-06 18:59 ` David Stacey
2014-04-07 18:54 ` Reini Urban
2014-04-07 19:30 ` Achim Gratz
2014-04-07 21:31 ` Reini Urban
2014-04-08 18:02 ` Achim Gratz
2014-04-08 20:52 ` Reini Urban
2014-04-08 21:27 ` Achim Gratz
2014-04-09 14:13 ` Reini Urban
2014-04-09 5:20 ` Yaakov (Cygwin/X)
2014-04-09 18:02 ` Achim Gratz
2014-05-02 8:22 ` perl-5.18.2-1 (was: 64-bit: Missing perl modules) Achim Gratz
2014-05-03 2:06 ` Ken Brown [this message]
2014-05-04 5:51 ` perl-5.18.2-1 Yaakov (Cygwin/X)
2014-05-04 7:29 ` perl-5.18.2-1 Achim Gratz
2014-05-04 8:24 ` perl-5.18.2-1 Yaakov (Cygwin/X)
2014-05-04 9:36 ` perl-5.18.2-1 Achim Gratz
2014-05-11 19:05 ` perl-5.18.2-1 Achim Gratz
2014-08-15 20:38 ` perl-5.18.2-1 Achim Gratz
2014-08-15 21:15 ` perl-5.18.2-1 Yaakov Selkowitz
2014-08-15 22:01 ` perl-5.18.2-1 David Stacey
2014-08-15 22:17 ` perl-5.18.2-1 Yaakov Selkowitz
2014-08-16 7:00 ` perl-5.18.2-1 Achim Gratz
2014-08-16 7:05 ` perl-5.18.2-1 Achim Gratz
2014-10-28 16:41 ` perl-5.18.2-1 Ken Brown
2014-10-29 11:17 ` perl-5.18.2-1 Corinna Vinschen
2014-10-30 8:00 ` perl-5.18.2-1 Reini Urban
2014-10-30 16:58 ` perl-5.18.2-1 Achim Gratz
2014-11-03 22:09 ` perl-5.18.2-1 Ken Brown
2014-11-04 16:25 ` perl-5.18.2-1 Achim Gratz
2014-11-10 21:30 ` perl-5.18.2-1 Ken Brown
2014-05-04 17:20 ` perl-5.18.2-1 Achim Gratz
2014-05-04 17:59 ` perl-5.18.2-1 Ken Brown
2014-04-08 16:20 ` 64-bit: Missing perl modules David Stacey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53644EFC.1090703@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).