On Mon, Mar 17, 2008 at 10:30:51AM -0000, Norbert Preining wrote:
> On Fr, 01 Feb 2008, Launchpad Bug Tracker wrote:
> > I have a personal texmf.cnf file which only override selected paths, compared to the system texmf.cnf.
>
> Where is the local texmf.cnf?
In my home directory. Does it matter?
> What is the TEXMFCNF?
The environment which specifies where to find the texmf.cnf config file.
However, I found the bug. tex-live appears to put all the ls-R
index files in a central directory, and consequently they cannot
be updated by a user. It follows that under tex-live, a user
texmf tree has to be searched explicitely without using an ls-R
index.
The problem is the same with a native installation of tex-live.
On Mon, Mar 17, 2008 at 10:30:51AM -0000, Norbert Preining wrote:
> On Fr, 01 Feb 2008, Launchpad Bug Tracker wrote:
> > I have a personal texmf.cnf file which only override selected paths, compared to the system texmf.cnf.
>
> Where is the local texmf.cnf?
In my home directory. Does it matter?
> What is the TEXMFCNF?
The environment which specifies where to find the texmf.cnf config file.
However, I found the bug. tex-live appears to put all the ls-R
index files in a central directory, and consequently they cannot
be updated by a user. It follows that under tex-live, a user
texmf tree has to be searched explicitely without using an ls-R
index.
The problem is the same with a native installation of tex-live.
:-- george