Re: lmodern package ready for teTeX 3 and upgrades from sarge
On Sun, Oct 09, 2005 at 20:53 +0200, Florent Rougon wrote:
> Ralf Stubner <ralf.stubner@web.de> wrote:
>
> Is that so expensive to scan $TEXMFSYSVAR that it would be worth it to
> drop this (admittedly seldom useful) safety net?
Scanning $TEXMFSYSVAR is cheap. Scanning all TEXMF trees could be
problematic for 'power users' that have lots of additional packages
installed in $TEXMFLOCAL. Your suggestion of only refreshing
$TEXMFSYSVAR and $TEXMFMAIN is probably the best compromise here.
> > All other files are installed in $TEXMFMAIN.
>
> But maybe this could change with on-the-fly PFB extraction. :)
Maybe. :-) Although, it would be quite similar to the current situation
with pk fonts, if compressed t1c files are installed in $TEXMFMAIN and
the pfb files get written to $VARTEXFONTS. The ls-R files for
$VARTEXFONTS would get updated by 'mktexpfb'.
> That is why updmap complains. It cannot stand seeing files in obsolete
> locations. If you remove the /usr/share/texmf/dvips/config symlink prior
> to installing lmodern, everything works fine with no warning. But other
> packages such as hlatex-fonts-base are not yet ready for that.
I still had problems understanding it, so I simply installed
0.92-8+tetex3+5 on my Sarge system with Frank's teTeX 3 backport. I do
indeed get the warning from updmap you quoted. The reason for this
warning seems to be /etc/texmf/dvips/lm.map which is left behind from
the previously installed version. If I simply remove this file,
updmap-sys runs without any warnings. One could try to remove this file
in the maintainer scripts if it has not been changed (tetex-{base,extra}
does this) or simply document it in NEWS or something like that.
BTW, I don't think that removing the /usr/share/texmf/dvips/config
symlink would be a proper solution. After all, there are still config.*
files for dvips in /etc/texmf/dvips/.
Yet another BTW, in the README.Debian you mention using the LM fonts
with plain TeX and give a simple example. For simple things this does
indeed work, but something like
\font\lmtenrm=cork-lmr10
\lmtenrm ÿ ß \ss \l \H{u}
\tenrm \ss \l \H{u}
\end
fails miserably. So at least a warning that the fonts are T1/EC/Cork
encoded would be useful IMHO.
cheerio
ralf
Reply to: