This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: perl_vendor
- From: Reini Urban <rurban at x-ray dot at>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 17 Sep 2012 12:57:35 -0500
- Subject: Re: perl_vendor
- References: <87a9ybqddk.fsf@Rainer.invalid> <CAHiT=DGLyTQymCmAJO-nU6Xhi+QrAMjAHqov5KZsT_24Gb48nQ@mail.gmail.com> <871uio8huf.fsf@Rainer.invalid>
On Thu, Aug 30, 2012 at 11:28 AM, Achim Gratz wrote:
> Reini Urban writes:
>> What's the problem? Lack of upates for these?
>
> My problem is that I need quite a bunch of additional Perl
> distributions, I need to package them into Cygwin packages since they
> will need to be installed with setup.exe and the way things are bundled
> in perl_vendor makes dependency tracking more difficult.
Which one? I have no idea.
When you start proposing your stuff I can remove these packages
from perl_vendor.
But I still don't get the point. Now you have one dependency: perl_vendor.
With your scheme you have many dependencies.
> I already have a solution, I simply don't use perl_vendor and re-package everything I
> need from it (essentially all of it, so the selection is quite sound).
> That's what I linked to, I wasn't proposing that everything in this
> bundle should go into Cygwin.
>
> I won't bring this up again, I think everybody has said what they wanted
> to say.
You need to bring this up when you ITP them.
Because clashes are disallowed. You cannot provide the same files
with different packages.
--
Reini Urban
http://cpanel.net/ http://www.perl-compiler.org/