From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: perl-5.24?
Date: Fri, 07 Apr 2017 21:57:00 -0000 [thread overview]
Message-ID: <c256d1c6-b511-4401-1fd7-a1a6a4d7868d@cornell.edu> (raw)
In-Reply-To: <809dcad6-e168-ce2c-1576-fec00c72d6cd@cornell.edu>
On 7/18/2016 8:03 AM, Ken Brown wrote:
> On 7/18/2016 3:39 AM, Achim Gratz wrote:
>> Ken Brown <kbrown@...> writes:
>>> I'm wondering whether you have plans to update perl to 5.24. The biber
>>> developer has just announced that the next version of biber will require
>>> it because "they have the postfix dereference notion officially
>>> supported and I can get rid of the the horrible circumfix operator
>>> syntax".
>>
>> The RC1 for 5.24.1 is available now. If it's binary compatible with the
>> 5.22 modules, I could update Perl without too much trouble, I think.
>
> Thanks. The INSTALL file says that it's not binary compatible and that
> XS modules will have to be recompiled. It looks like we have about 8 of
> those in the distro.
It looks like 5.26.0 is due to be released in a couple weeks. What are
your plans for updating? Do you think it might happen in time for TeX
Live 2017 (expected to be released in late May or early June)? If not,
I'll probably have to temporarily go back to the old system of shipping
biber as a packed Perl archive.
Thanks.
Ken
next prev parent reply other threads:[~2017-04-07 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 13:57 perl-5.24? Ken Brown
2016-07-07 15:46 ` perl-5.24? Achim Gratz
2016-07-18 7:40 ` perl-5.24? Achim Gratz
2016-07-18 12:03 ` perl-5.24? Ken Brown
2017-04-07 21:57 ` Ken Brown [this message]
2017-04-08 6:42 ` perl-5.24? Achim Gratz
2017-04-08 16:55 ` perl-5.24? Achim Gratz
2017-04-08 21:10 ` perl-5.24? Ken Brown
2017-04-09 6:36 ` perl-5.24? Achim Gratz
2017-04-09 9:50 ` perl-5.24? 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=c256d1c6-b511-4401-1fd7-a1a6a4d7868d@cornell.edu \
--to=kbrown@cornell.edu \
--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).