This is the mail archive of the
mailing list for the Cygwin project.
[64bit] Biber packaging questions
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin-apps <cygwin-apps at cygwin dot com>
- Cc: Philip Kime <philkime at kime dot org dot uk>
- Date: Wed, 12 Jun 2013 10:10:07 -0400
- Subject: [64bit] Biber packaging questions
I've succeeded, with help from the Biber developer, in building
biber.exe for 64bit Cygwin. This is supposed to be part of
texlive-collection-bibtexextra. Before I send an RFU, I have a few
packaging questions, for which I have to give some background.
Biber is written in perl and is then packed into a self-contained Perl
Archive biber.exe. The first time a user runs biber.exe, it unpacks all
necessary perl modules and all necessary DLLs (including the perl DLL)
into a subdirectory of /tmp. In this way biber.exe can run on any
Cygwin system, which doesn't even have to have perl installed. In order
to *build* biber.exe, however, perl and many perl modules are required.
The Biber developer builds the executables for several platforms
(including 32bit Cygwin). These executables are then included in the
TeX Live source. Since he does not currently build biber.exe for 64bit
Cygwin, I had to do this step. This required building the following
perl modules, which are not currently in the Cygwin distro:
Here are my questions:
1. Should these build prerequisites be added to the 64bit distro?
Otherwise it will be difficult for others to rebuild biber from source.
2. Biber requires perl 5.16 or later, so I did a quick and dirty build
of perl-5.16.3. By "quick and dirty" I mean that I simply took Yaakov's
perl.cygport and removed all patches that wouldn't apply. This is no
problem for *users* of biber.exe, since the latter includes the perl
DLL. But again it makes it difficult for others to replicate the build
until the official perl is updated. I have no idea what to do about this.
3. There is a completely different approach I could take. Namely, I
could simply package Biber as a perl module and forget about packing it
into a Perl Archive. If I do this, then users will need perl 5.16 or
later, as well as most or all of the perl modules listed above, so the
RFU will have to wait for a perl update; but that's probably not
serious. Would this be preferable? I'm not aware of any Linux distros
that do this, though someone did do it unofficially for Fedora:
P.S. I'm copying Philip Kime, the Biber developer. He should probably
be kept in the CC for all replies.