From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: perl-5.22.0-RC2 / Perl distributions
Date: Fri, 10 Jul 2015 18:30:00 -0000 [thread overview]
Message-ID: <55A00F2B.6060401@cornell.edu> (raw)
In-Reply-To: <55636DAE.8020607@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On 5/25/2015 2:45 PM, Ken Brown wrote:
> BTW, I contacted Philip Kime, the author of Biber, about
> Unicode::Normalize. He told me that version 1.18 is unusably slow.
> Here's a bug report he filed about it:
>
> https://rt.cpan.org/Public/Bug/Display.html?id=102766
>
> I think he's planning to pursue it further.
It doesn't look like anything is going to change in the near future.
According to the bug report I cited, Biber runs slower by a factor of 20
with version 1.18 of Unicode::Normalize than with version 1.17. I don't
think that's acceptable.
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.
Does anyone have a better idea?
Ken
[*] This is the way Biber is shipped by TeX Live on all platforms on
which the Biber author can build it. This includes i686-cygwin but not
x86_64-cygwin, because he doesn't have a 64-bit Cygwin system. But I am
expecting to build it on x86_64-cygwin and send it upstream for
inclusion in TeX Live. I already have it built and just need to do a
little more testing.
[-- Attachment #2: perl-Unicode-Normalize.cygport --]
[-- Type: text/plain, Size: 335 bytes --]
NAME="perl-Unicode-Normalize"
VERSION="1.17"
RELEASE="1"
CPAN_AUTHOR="SADAHIRO"
DESCRIPTION="Perl distribution Unicode-Normalize, providing Perl modules:
Unicode::Normalize.
Unicode Normalization Forms."
DIFF_EXCLUDES="MYMETA.*"
inherit perl
SRC_URI="http://backpan.perl.org/authors/id/S/SA/SADAHIRO/Unicode-Normalize-1.17.tar.gz"
next prev parent reply other threads:[~2015-07-10 18:30 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 [this message]
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=55A00F2B.6060401@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).