> Same here (Redhat 7.x). I guess it depends on an environment > variable TEXMF<something> being set in a system-wide profile > to work from scratch.
No, see my previous mail. > ### SU: added using `kpsewhich' as last fallback before giving up; since > ### xdvik is most likely to be installed with an *existing* kpathsearch > ### system, this seemed reasonable to me. > texmfmain=`kpsewhich --expand-path='$TEXMFMAIN' 2>/dev/null | sed 's,//*,/,g'` While this makes sense for a single driver, I don't recommend this for complete systems like teTeX. People might be suprised if files get installed into their old system even though a new prefix was chosen. > I don't know whether it might be reasonable to have this in the > default installation as well; IMHO it's harmless when kpathsearch > isn't installed yet or an obsolete version that doesn't provide > --expand-path (teTeX 0.4?), and rather useful else ... Thomas, > what do you think about this? teTeX-0.4 does not set TEXMFMAIN, so there is little you could do about it. You could examine the result of kpsexpand '$TEXMF' Thomas
