For a usb stick install, it would be nice if there were no
hard-coded paths anywhere. A texmfcnf.lua with content
return {
TEXMFCACHE = kpse.var_value('TEXMFSYSVAR')
}
appears to be read but ignored. Moreover, the fndb lua files under
luatex-cache/context/xxx/trees contain hard-coded paths.
On Sat, Mar 12, 2011 at 10:32 AM, Siep Kroonenberg si...@cybercomm.nl wrote:
For a usb stick install, it would be nice if there were no
hard-coded paths anywhere. A texmfcnf.lua with content
return {
TEXMFCACHE = kpse.var_value('TEXMFSYSVAR')
}
appears to be read but ignored. Moreover,
On Sat, Mar 12, 2011 at 10:44:49AM +0100, luigi scarso wrote:
On Sat, Mar 12, 2011 at 10:32 AM, Siep Kroonenberg si...@cybercomm.nl wrote:
For a usb stick install, it would be nice if there were no
hard-coded paths anywhere. A texmfcnf.lua with content
return {
TEXMFCACHE =
On Sat, Mar 12, 2011 at 10:53, Siep Kroonenberg wrote:
Is there any way to avoid hard-coded paths?
Isn't minimals path-aware ?
With setuptex I can put context wherever I want.
This is in the context of TeX Live. But I'll have a look at how
minimals does it.
This has been changed after the
On Sat, Mar 12, 2011 at 03:03:34PM +0100, Mojca Miklavec wrote:
On Sat, Mar 12, 2011 at 10:53, Siep Kroonenberg wrote:
Is there any way to avoid hard-coded paths?
Isn't minimals path-aware ?
With setuptex I can put context wherever I want.
This is in the context of TeX Live. But I'll
