[tex-live] mtxrun should write user luatex-cache to a user directory

[Vladimir Lomov]

** Mojca Miklavec [2011-08-01 14:20:06 +0200]:

> On Mon, Aug 1, 2011 at 14:12, Vladimir Lomov <lomov.vl at gmail.com> wrote:
>> Hi.
>> According to $TEXLIVEROOT/texmf/web2c/texmfcnf.lua
>> the generated cache is placed in TEXMFSYSVAR but not in
>> TEXMFVAR[=$HOME/.texlive2011/texmf-var].

>> Is that on purpose or just a "bug"?

>> Offending lines in texmfcnf.lua:
>> [file="texmfcnf.lua"]
>> ...
>>            -- We have only one cache path but there can be more. The first writable one
>>            -- will be chosen but there can be more readable paths.

>>            TEXMFCACHE      = "$TEXMFSYSVAR;$TEXMFVAR",
>>            TEXMFCONFIG     = "home:.texlive2011/texmf-config",
>> ...
>> [/file]

> If TEXMFSYSVAR is writable, the cache goes to TEXMFSYSVAR. If it is
> not, the cache goes to TEXMFVAR. The idea behind this is that
> installer updates the cache when new packages are added, while users
> can still generate their own cache.

> Do you experience any problems with that?
No, but I was surprised when I run
user $ OSFONTDIR="/usr/share/fonts//" mtxrun --generate
that cache goes to TXMFSYSVAR but not in mine TEXMFVAR.

Actually I consider this as a bug, because if TEXMFSYSVAR
is writable then when any user run 'mtxrun --generate' the would be only
_one_ cache for _all_ users (imagine two users on the system, one has
commercial font other is not).

When installer is run it should use, of course, TEXMFSYSVAR. Right now I
don't have any pretty solution (only temporary: swap variables before
run mtxrun then back).

---
WBR, Vladimir Lomov

-- 
	A novice was trying to fix a broken lisp machine by turning the
power off and on.  Knight, seeing what the student was doing spoke sternly,
"You cannot fix a machine by just power-cycling it with no understanding
of what is going wrong."  Knight turned the machine off and on.  The
machine worked.