From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: perl-5.22.0-RC2 / Perl distributions
Date: Fri, 10 Jul 2015 21:32:00 -0000 [thread overview]
Message-ID: <87fv4v8zrs.fsf@Rainer.invalid> (raw)
In-Reply-To: <55A00F2B.6060401@cornell.edu> (Ken Brown's message of "Fri, 10 Jul 2015 14:30:03 -0400")
Ken Brown writes:
> The only solution I can think of is to ship Biber as a self-contained
> Perl Archive made with PAR::Packer[*], built with version 1.17 of
> Unicode::Normalize. I've gotten the latter from backpan and built it
> locally using the attached cygport file.
At the moment, judging from the ChangeLog, the only change for 1.18 was
the removal of the XS code. So if that module still builds and works OK
on 5.22 even though the API it is using has been deprecated, I think
Cygwin should ship 1.17 as default until things are sorted out upstream.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2015-07-10 21:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 20:03 Achim Gratz
2015-05-24 21:03 ` Ken Brown
2015-05-25 7:01 ` Achim Gratz
2015-06-05 16:44 ` Eric Blake
2015-05-25 2:26 ` Ken Brown
2015-05-25 7:00 ` Achim Gratz
2015-05-25 13:13 ` Ken Brown
2015-05-25 15:21 ` Achim Gratz
2015-05-25 16:41 ` Ken Brown
2015-05-25 18:31 ` Achim Gratz
2015-05-25 18:45 ` Ken Brown
2015-07-10 18:30 ` Ken Brown
2015-07-10 19:33 ` Yaakov Selkowitz
2015-07-10 19:45 ` Ken Brown
2015-07-10 21:32 ` Achim Gratz [this message]
2015-07-10 22:27 ` Yaakov Selkowitz
2015-07-14 20:00 ` Achim Gratz
2015-10-20 19:31 ` Unicode-Normalize [Re: perl-5.22.0-RC2 / Perl distributions] Achim Gratz
2015-10-20 22:49 ` Ken Brown
2015-10-27 19:51 ` Ken Brown
2015-11-01 19:06 ` Achim Gratz
2015-05-25 22:55 ` perl-5.22.0-RC2 / Perl distributions David Stacey
2015-05-26 5:32 ` Achim Gratz
2015-05-26 8:35 ` David Stacey
2015-05-26 16:41 ` 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=87fv4v8zrs.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).