Re: tex-common and TEXMFSYSCONFIG
Norbert Preining wrote:
> Playing around with the texlive packages I found the following:
>
> It is disturbing that TEXMFSYSCONFIG = TEXMFMAIN.
>
> Why: If you want to override a map file (in my case belleek.map) I
> thought it might be a good idea to put an empty belleek.map into
> /usr/local/share/texmf. But alas,updmap-sys still uses the one in
> TEXMFMAIN, because it uses the one in TEXMFCONFGI.
>
> I cannot recall this decision, did we have a purpose for setting it this
> way and not to TEXMFLOCAL?
I don't remeber when this has been discussed. However, there has been
some discussion on TEXMFSYSCONFIG and problems related to it recently.
See http://lists.debian.org/debian-tetex-maint/2005/11/msg00112.html et al.
BTW, Norbert, in
http://lists.debian.org/debian-tetex-maint/2005/11/msg00414.html I found
some interoperability problems between your lmodern packages and ConTeXt
from teTeX 3.0. What's the situation like with TeX Live? Do you use the
separate lmodern package? If yes, I would expect similar problems there,
but the other way round.
In general, this looks like a nasty problem to me: ConTeXt is highly
integrated. I don't know if it is possible to replace some files within
it. So it looks like a given version of ConTeXt will only work with a
given version of lmodern (at least for the moment). This makes it
difficult to use a separate lmodern package for both teTeX and TeX Live.
cheerio
ralf
Reply to: