lmodern package ready for teTeX 3 and upgrades from sarge
Hi,
It's been a long time since there is an lmodern package that
specifically uses the teTeX 3 infrastructure (new upate-updmap and new
TDS version) on:
deb http://people.debian.org/~frn/teTeX-3.0 sid/binary-all/
deb-src http://people.debian.org/~frn/teTeX-3.0 sid/source/
The news is that lmodern 0.92-8+tetex3+4 is designed to handle the
upgrade from the previous versions (most notably, from the package in
sarge, which uses the "old updmap scheme"). It should work; you can try
it. I consider it ready for unstable (but the package uploaded to
unstable will be numbered 0.92-8 and will have to wait for the upload of
teTeX 3).
I've also uploaded the previous version (0.92-8+tetex3+3), which is
almost the same as 0.92-7+tetex3+3 (cosmetic fixes,
s/VARTEXMF/TEXMFSYSVAR/g in comments...). The purpose of this version is
(as what could already be found in this repository) to provide a sample
font package that uses the "new updmap scheme" (the update-updmap we
have in teTeX 3). 0.92-8+tetex3+4 is not as good for this purpose
because handling the upgrade from teTeX 2 times makes the maintainer
scripts more complex than needed for a package that is first uploaded in
the teTeX 3 era[1]. Newly created packages don't need this complexity.
Based on Ralf's comments, maybe it might be better to use mkfontscale,
at least with respect to the declared charsets. I believe I didn't
evaluate this tool when I added the X support to lmodern (maybe it
wasn't available yet?). FYI, I generate my fonts.scale file with sed at
build time from the defoma hints file, which I wrote manually (this is
good to get families, weights, etc. right, but choosing which encoding
to declare based on unknown rules is not very easy). Otherwise, the ways
things are done there should be safe; in particular, the order of the
update-updmap, mktexlsr and updmap-sys calls in postinst and postrm is
_the_ good one, AFAICT.
As usual, lintian complains about stuff in /usr/X11R6/lib, but I think
it is wrong here: the stuff in question is only a bunch of symlinks, and
it is the place recommended by Policy § 11.8.5.4.
If you test 0.92-8+tetex3+4, you will probably see at configure time:
,----
| Running updmap-sys...
| !!! WARNING: Identical copy of used file for `lm.map'
| exists in obsolete location
| /usr/share/texmf/dvips/config/lm.map
| Please, consider removing this file.
|
|
|
| !!! NOTICE:
|
| With this release, the search paths for map files have been changed
| and we have found that some files exist in the new path as well as
| in the obsolete path.
|
| This is not an error per se, but please consider removing duplicates
| from the old location and search the above output or the transcript file
| /var/lib/texmf/web2c/updmap-sys.log
| for warnings.
|
| For more information about the changed search paths, see
| the release notes section in the teTeX manual. You probably
| can read this document by executing the command
| texdoc TETEXDOC
| else visit the web page
| http://tug.org/texlive/mapenc.html
|
| done.
`----
This cannot be solved in lmodern, AFAIK (without violating the new TDS).
It is caused by the /usr/share/texmf/dvips/config symlink installed by
tetex-base and I believe that I've already discussed about it with
Frank, and that he left it there for compatibility reasons. However,
users may be slightly upset by such a warning...
Regards,
[1] Question of the day: if this is called an era, how should we call
the duration of a Debian release cycle? :-)
--
Florent
Reply to: