[tex-live] TEXINPUTS problem

[Olaf Weber]

Thomas Esser writes:
> On Sun, Oct 17, 2004 at 11:53:24AM -0400, Karl Berry wrote:

>> As far as I know source and source.development should have exactly the
>> same files right now.  As far as texmf.in goes, it should be the same as
>> teTeX, again AFAIK.  TeX Live doesn't use it, as we know (see next message).

One thing that surprised me is that texmf/web2c/texmf.cnf contains
'original texmf.cnf --', which means that if you do a full build it
gets overwritten.  This is perhaps not a good thing.

> teTeX's search paths reflect precisely the needs for searching teTeX's
> texmf tree using the current status of our applications. This means that
> all search paths are set to the absolute minimum. My file differs in the
> following (typical) examples from Olaf's (- is web2c version; + is my
> version):

> "engine" level, I only have tex:
>     -TEXINPUTS.pdfmex   = .;$TEXMF/{pdftex,tex}/{mex,plain,generic,}//
>     +TEXINPUTS.pdfmex   = .;$TEXMF/tex/{mex,plain,generic,}//

I plead backward compatibility with older texmf trees.

> all format names unique, no subdir:
>     -TEXFORMATS = .;$TEXMF/web2c/{$engine,}//
>     +TEXFORMATS = .;$TEXMF/web2c

> bib / bst searching:
>     -BIBINPUTS = .;$TEXMF/bibtex/{bib,}//
>     -BSTINPUTS = .;$TEXMF/bibtex/{bst,}//
>     +BIBINPUTS = .;$TEXMF/bibtex/bib//
>     +BSTINPUTS = .;$TEXMF/bibtex/bst//

For this case, I'm envisioning "simplified" trees where all bibtex
related files are just under texmf/bibtex.  For example, a tree in
someone's home directory could be like that.

> So, the question is: what shall be in TL's sources, my settings or Olaf's?

> The other differences somehow should be cleaned up. By transforming
> all engine stuff to tex in Olaf's file, running a diff against my file,
> and removeing the above stuff, the remaining differences are:

> -TEXINPUTS.pdfxlatex = .;$TEXMF/tex/{latex,generic,}//
> -TEXINPUTS.pdfxtex   = .;$TEXMF/tex/{plain,generic,}//
> -TEXINPUTS.xelatex = .;$TEXMF/tex/{latex,generic,}//
> -TEXINPUTS.xetex   = .;$TEXMF/tex/{plain,generic,}//
> -OTFFONTS = .;$TEXMF/fonts/otf/{xetex,}//
> -TEXINPUTS.elambda = .;$TEXMF/tex/{lambda,latex,generic,}//
> -TEXINPUTS.eomega = .;$TEXMF/tex/{plain,generic,}//
> -TEXINPUTS.alambda = .;$TEXMF/tex/{lambda,latex,generic,}//
> -TEXINPUTS.lamed = .;$TEXMF/tex/{lambda,latex,generic,}//
> +TEXINPUTS.lamed = .;$TEXMF/tex/{lamed,lambda,latex,generic,}//

Not all of these are from my version, I think.

> Questions:
>   - shall I add pdfxlatex pdfxtex to my file (I guess yes)
>   - shall I add xelatex xetex? (Gerben?)
>   - why has xetex a special precedence within fonts/otf (for *all*
>     applications)? This looks wrong.
>   - drop elambda eomega alambda?
>   - which path for lamed (I have added lamed at the formats level)?

Note that TeX-live (and even teTeX) may be in a position to make
assumptions about the texmf trees that web2c cannot make.

> Thomas

> _______________________________________________
> TeX Live mailing list
> http://tug.org/mailman/listinfo/tex-live

-- 
Olaf Weber

               (This space left blank for technical reasons.)