[DVIPDFMx] [peb@mppmu.mpg.de: Towards TL2010 -- major update]

[Karl Berry]

Date: Tue, 10 Nov 2009 16:04:08 +0100 (CET)
From: Peter Breitenlohner <peb at mppmu.mpg.de>
To: Karl Berry <karl at freefriends.org>
cc: Yannis Haralambous <yannis.haralambous at telecom-bretagne.eu>,
   Taco Hoekwater <taco at elvenkind.com>, Thanh Han The <thanh at river-valley.org>,
   =?ISO-8859-15?Q?Martin_Schr=F6der?= <martin at oneiros.de>,
   Jonathan Kew <jfkthame at googlemail.com>,
   Jerome Laurens <jerome.laurens at u-bourgogne.fr>
Subject: Towards TL2010 -- major update

Hi Jerome, Jonathan, Karl, Martin, Taco, Thanh, and Yannis,

I have just finished a major update of TL SVN (r15981), accumulated in my
working tree during the last few month while TL was more or less frozen in
preparation for TL2009.

Some major changes are in the build system (unlimited parallel builds, no
more spurious rebuilds), update of a few libraries (including ICU-4.2.1 plus
patches for XeTeX), inclusion of bibtexu (with the possibility to use
installed ICU libraries -- while XeTeX at the same time uses the patched
ones from the TL tree), and adaption of luaTeX/pdfTeX to poppler-0.12.

In addition there were a few changes in Kpathsea and Web2C proper, i.e.,
web2c/web2c/ and web2c/lib/ mainly concerned with getting ALL extern
declarations from headers and with the handling of const.  Plus quite a few
changes in your code, but only to adjust to the Kpathsea/Web2C changes or to
avoid compiler warnings.

Another new feature is what I call 'build on demand': even for those parts
configured not to be built you can go to the corresponging directory in the
build tree and, e.g., say 'make etex' (or 'make etex.exe').  To be extreme,
you can configure with '--disable-all-pkgs' and run 'make' which will
configure all subdirectories but will neither build nor install anything. 
Nevertheless 'make' in, e.g., web2c/bitexu/ will first build the ICU and
kpathsea libraries (unless configured '--with-system-*') and then bibtexu.

Please update your repositories accordingly.  All modifications are listed
in ChangeLog files.  At the top-level there is a new file README.coding
explaining the ideas behind these changes; it would be extremely nice if you
could continue the work towards these ideas in your code.

Hi Karl,

can you please forward this to everyone else concerned, first of all the
maintainers of (x)dvipdfmx.

Regards
Peter Breitenlohner <peb at mppmu.mpg.de>