[64bit] Biber packaging questions

Reini Urban rurban@x-ray.at
Fri Jun 14 20:14:00 GMT 2013

On Fri, Jun 14, 2013 at 1:49 PM, Yaakov (Cygwin/X) wrote:
> On 2013-06-14 13:37, Reini Urban wrote:
>> I would just bundle them to something like a perl-biber-bundle
>> package, into vendor_perl.
> No, perl_vendor needs to go away, not get bigger.

I said vendor_perl, the location.
You meant perl_vendor the package.

> Since you need so many perl deps, do you really want to keep them seperate?

Yes, I would want _all_ non-core Perl distributions as separate cygwin
packages.  That's the only sane way to deal with these when the need for
local patches arises.  This is admittedly rare, but it does happen.

If you really want to maintain 2000+ packages do it. I don't care.
I hope you know what happens over at debian, macports and redhat with
this scheme. Been there, done that.
Also, our UI setup selector cannot handle that.
At cygwin we favor cpan over cygwin packages.
If the urgent need for a local patch arises the user can always cpan
it, until the lazy maintainer updates his package.
Reini Urban
http://cpanel.net/   http://www.perl-compiler.org/

More information about the Cygwin-apps mailing list