From: Reini Urban <rurban@x-ray.at>
To: cygwin-apps@cygwin.com
Subject: Re: perl_vendor
Date: Mon, 17 Sep 2012 17:57:00 -0000 [thread overview]
Message-ID: <CAHiT=DG5B1Od_4qeYkHrQf0NMPStzoB4Qa-JrVf-v9CRn7P7zA@mail.gmail.com> (raw)
In-Reply-To: <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/
next prev parent reply other threads:[~2012-09-17 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 8:18 perl_vendor Achim Gratz
2012-08-29 23:52 ` perl_vendor Yaakov (Cygwin/X)
2012-08-30 16:32 ` perl_vendor Achim Gratz
2012-08-30 15:08 ` perl_vendor Reini Urban
2012-08-30 16:28 ` perl_vendor Achim Gratz
2012-09-17 17:57 ` Reini Urban [this message]
2012-10-01 18:23 ` perl_vendor Achim Gratz
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='CAHiT=DG5B1Od_4qeYkHrQf0NMPStzoB4Qa-JrVf-v9CRn7P7zA@mail.gmail.com' \
--to=rurban@x-ray.at \
--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).