[tex-live] TEXINPUTS problem

[Thomas Esser]

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).

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,}//

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//

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,}//

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)?

Thomas