[tex-live] Has anything changed in the order TL searches for packages?

Urs Liska lists at openlilylib.org
Wed May 16 17:16:39 CEST 2018


Hm,

I have

    /etc/texmf/web2c/texmf.cnf
    /usr/share/texlive/texmf-dist/web2c/texmf.cnf
    /usr/share/texmf/web2c/texmf.cnf

The first two only contain a reference to VARTEXFONTS, which is not what 
we're talking about.

The third one seems to be the same you quote.

    $env

doesn't return anything that seems to relate to TeX at all.

I had been at a loss right from the start, but it keeps getting stranger 
by the minute ...

Urs


Am 16.05.2018 um 16:50 schrieb Zdenek Wagner:
> It seems that you have TL from a Debian package, so I cannot be 
> specific. Anyway, after fresh update (using TL from TUG) I see that 
> ~/texmf is searched first. Specificaly my .../web2c/texmf.cnf says:
>
> % List all the texmf trees. For an explanation of what they are, see the
> % TeX Live manual.
> %
> % For texconfig to work properly, TEXMFCONFIG and TEXMFVAR should be named
> % explicitly and before other trees.
> %
> % TEXMFLOCAL precedes TEXMFDIST because locally-installed versions
> % should take precedence over distribution files -- although it is
> % generally a source of confusion to have different versions of a
> % package installed, whatever the trees, so try to avoid it.
> %
> % The odd-looking $TEXMFAUXTREES$TEXMF... construct is so that if no 
> auxtree is
> % ever defined (the 99% common case), no extra elements will be added to
> % the search paths. tlmgr takes care to end any value with a trailing 
> comma.
> TEXMF = 
> {$TEXMFAUXTREES$TEXMFCONFIG,$TEXMFVAR,$TEXMFHOME,!!$TEXMFLOCAL,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFDIST}
>
> Maybe you have some forgotten TeX specific environment variable or 
> your local texmf.cnf
>
>
> Zdeněk Wagner
> http://ttsm.icpf.cas.cz/team/wagner.shtml
> http://icebearsoft.euweb.cz
>
> 2018-05-16 16:42 GMT+02:00 Urs Liska <lists at openlilylib.org 
> <mailto:lists at openlilylib.org>>:
>
>     Hi Zdenek and Norbert,
>
>     thanks for the clarification. Unfortunately it doesn't help:
>
>         $ kpsewhich lyluatex.sty -engine lualatex
>         /home/uliska/texmf/tex/latex/latex-git/lyluatex/lyluatex.sty
>
>         $ kpsewhich lyluatex.sty -engine luatex
>         /home/uliska/texmf/tex/latex/latex-git/lyluatex/lyluatex.sty
>
>     both point to the "local" file.
>     Moving the local package to ~texmf/tex/luatex doesn't help either,
>     i.e. still the texlive version is found.
>
>     I just checked with another custom package (that has not been
>     published) to see whether ~/texmf is searched at all, and there's
>     no issue with that.
>
>     So it seems that /usr/share/texlive is searched before ~/texmf,
>     regardless of the engine.
>
>     Is there some configuration file that may have to be changed, that
>     may have been overwritten by the update, or that is simply
>     different between ~/.texlive2017 and ~/.texlive2018?
>
>     Urs
>
>
>     Am 16.05.2018 um 16:33 schrieb Norbert Preining:
>>     That a problem with TDS. You are not putting lyluatex into the search path of luatex, but latex.
>>
>>     Follow the layout of the original lyluatex package, that is, put it into texmf/luatex/lyluatex
>>
>>     You can reproduce this behavior by using -engine luatex with kpsewhich.
>>
>>     Norbert
>>
>>
>>     --
>>     PREINING Norberthttp://www.preining.info
>>     Accelia Inc. + JAIST + TeX Live + Debian Developer
>>     GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/tex-live/attachments/20180516/16051aa7/attachment-0001.html>


More information about the tex-live mailing list