[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#607857: tex-common: Hard-coded path in proposed patch



On Di, 28 Dez 2010, Hilmar Preusse wrote:
> > AFAIK the paths texlive uses can be freely configured by the sysadmin.
> > So I think the paths /var/lib/texmf/ etc in the examples are
> > simplification to clearly state the idea and not meant to appear
> > in real code.
> > 
> > Therefore I suggest to modify the proposed patch of ponstinst.in to 
> > obtain the path from the relevant configuration variable
> > (which I guess is TEXMFSYSVAR as this seems to be the one used by 
> > updmap-sys).

I disagree. The path can in principle be changed in texmf.cnf, but this
is not what we support.

Most of our scripts (the ones written for Debian) expect TEXMFDIST to 
be /u/s/texmf-texlive and TEXMFSYSVAR to be /v/l/texmf.

Looking through the whole trigger code I see many instances of that.

To make it completely clear: Debian TeX Live does not support
moving of arbitrary trees by changing variables in texmf.cnf.

If we allow that this will be a huge set of worms we open up.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
HOFF (vb.)
To deny indignantly something which is palpably true.
			--- Douglas Adams, The Meaning of Liff



Reply to: