public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: perl-5.22.0-RC2 / Perl distributions
Date: Mon, 25 May 2015 13:13:00 -0000	[thread overview]
Message-ID: <55631FDB.10201@cornell.edu> (raw)
In-Reply-To: <87iobh3zwg.fsf@Rainer.invalid>

On 5/25/2015 3:00 AM, Achim Gratz wrote:
> Ken Brown writes:
>> The latest version of Biber requires autovivification, XML::Writer,
>> and Text::Roman.  And Test::Difference is required for running the
>> tests.  Can you add those?
>
> I have the first two already from my last look at Biber… OK, the rest is
> now up, too.

I don't see XML::Writer.

>> Here's a trickier one: Biber wants Unicode::Normalize, version <=
>> 1.17.  There's a comment that says "1.18 removes XS and is too slow".
>> I'm not sure what to do about that.  Any advice?
>
> That is due to a deprecation in Perl 5.20 and later:
>
> --8<---------------cut here---------------start------------->8---
> Revision history for Perl extension Unicode::Normalize.
>
> 1.18  Tue May 27 22:04:23 2014
>      - XSUB is now deprecated and removed. see perl 5.20.0,
>        perldelta, Internal Changes, deprecation of uvuni_to_utf8 etc.
> --8<---------------cut here---------------end--------------->8---
>
> I don't know if it's still possible to build on 5.22, depending on where
> in the deprecation cycle we are with that function.  But the earlier
> module versions have been pulled from CPAN anyway and only 1.18 is
> available.  If it's just "too slow", then why do the Biber folks care?

I don't know.  I'm about to go on vacation, so I'll worry about this when I get 
back.  It's not relevant to the transition to perl-5.22.0.  My plan for the 
transition is to build biber-1.8 (x86_64 only for now), assuming it builds and 
tests OK once I have perl-XML-Writer.

Ken

  reply	other threads:[~2015-05-25 13:13 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 [this message]
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
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=55631FDB.10201@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).