Message-ID: <43AAFAFE.3010208@users.sourceforge.net>
Date: Thu, 22 Dec 2005 13:14:06 -0600
From: "Yaakov S (Cygwin Ports)" <yselkowitz@users.sourceforge.net>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: perl Bundle::Cygwin / perl-bundle-cygwin package
References: <20051222174601.GB3764@efn.org>
In-Reply-To: <20051222174601.GB3764@efn.org>
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

Yitzchak Scott-Thoennes wrote:
> I'm working on creating a bundle of common Perl modules that build and
> pass all significant tests on cygwin.
> 
> I hope to have it accepted as a cygwin package.

I think it's preferable to make separate packages for each module.  My
reasoning:

1) this is the precedent set by Linux distributions;
2) bumping one module doesn't require rolling a whole bundle;
3) separate modules minimizes unnecessary dependencies;
4) I'm sure there's something else I'm forgetting.

IOW, I do NOT like this idea.

If, OTOH, I do believe that more perl modules should go into the distro,
without packaging the entire CPAN, certainly:

1) modules which don't build OOTB (e.g. Tk, gtk2-perl bindings, etc.);
2) modules which are prerequisites for other packages (e.g.
ExtUtils::PkgConfig, necessary for building gtk2-perl bindings).

The same would apply, of course, to python and ruby.  You'll see I
already have a large selection on Cygwin Ports, although not all of
those are candidates for the distro.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDqvr8piWmPGlmQSMRAhnVAKCQet3+iSEXzFGKuJzkQ2VFt6O8cACgmpOJ
DxFLRP7JaFkj1l/LmGaoezA=
=Y/CB
-----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/