From: Reini Urban <rurban@x-ray.at>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: 64-bit: Missing perl modules
Date: Mon, 07 Apr 2014 18:54:00 -0000 [thread overview]
Message-ID: <CAHiT=DF117Jf0jdV8KQHOakkOw3_A5FvmSRKRRVnXGt-MLY6cA@mail.gmail.com> (raw)
In-Reply-To: <5341A3F5.2040506@tiscali.co.uk>
On Sun, Apr 6, 2014 at 1:59 PM, David Stacey wrote:
> On 06/04/14 17:38, Achim Gratz wrote:
>>
>> David Stacey writes:
>>>
>>> Thank you for your reply. Yes, I was aware of that discussion. I'm not
>>> talking about breaking up 'perl_vendor' for 32-bit Cygwin (although
>>> IMHO that would be a good thing in the long term). I'd just like to
>>> see the perl modules I mentioned adding to 64-bit Cygwin - and I'm
>>> happy to maintain those packages myself if no-one else want to claim
>>> ownership.
>>
>> I don't see why it should be a good idea to have different packaging for
>> the two architectures, so I still think this issue needs to be decided.
>
>
> Agreed. Hopefully the different collections of perl modules that are
> available in the two architectures can be unified with the next perl
> release.
>
>
>> Anyway, here's what I have:
>
>
> Yes, those are more or less identical to the packages that I prepared - I
> could have done with those links a few days ago :-) It's rather nice (albeit
> inefficient) to have two people trying to do the same thing - so often in
> open source programmes no-one has the time! You've obviously put some
> thought and effort into this, so I'm happy to step back and let you (or
> Reini) to maintain these perl modules. The important thing is that they end
> up in 64-bit Cygwin at some point.
>
> Thankfully, cygport makes most perl modules absurdly easy to maintain. So if
> you need someone to adopt a few if and when 'perl_vendor' gets split up then
> please let me know.
>
> Dave.
The new 5.18.2 package will be unified for 32bit and 64bit, yes.
perl_vendor will probably stay as is, as it is the easiest for the
user and the maintainer.
I still need to rebase all most-used XS modules esp. on 32bit perl to
make sense and avoid dll base collisions on forks, which happens with
CPAN, a basic bootstrap problem.
My cygwin-specific rebase framework for CPAN modules still needs some
love, esp. on 32bit.
--
Reini Urban
http://cpanel.net/ http://www.perl-compiler.org/
next prev parent reply other threads:[~2014-04-07 18:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 21:42 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 [this message]
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 ` perl-5.18.2-1 Ken Brown
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='CAHiT=DF117Jf0jdV8KQHOakkOw3_A5FvmSRKRRVnXGt-MLY6cA@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).