Oliver Buerschaper wrote:
Any ideas if getting rid of dependency on environmental variables is doable? I agree it would be great if mtxrun could call/do setuptex on itself if needed.
At the moment for me it would be enough to know where exactly LuaTeX looks for configuration information (path & file name) and which files take precedence over others in the case of conflicts ... my current understanding is:
1. Environment variables 2. setuptex.tmf
no, this one is only used when you run mtxrun --tree=.... i use this methos in web driven workflows where we can have multiple trees alongside (linux servers) and i never bother to setup my shell for that; i just call mtxrun then
3. texmf-context/web2c/context.cnf
we ship context.cnfas an example of what is needed (it's the one on my machine)
4. texmf/web2c/texmf.cnf
that one indeed unless it's in a usual place
5. ...
$TEXMF $TEXMFCACHE (since there is no agreement over where it lives) so, only two variables
As a second step, one would have to know what each of the settings in the above places is needed for. In particular, I would like to know which settings LuaTeX actually uses and which ones it ignores. But this can wait until the first question is figured out completely ;-)
$TEXMF is needed in order to locate the configuration file (currently still a CNF file but we may as well get rid of it since we use less and less info from it; if we would organize the minimals differently i.e. more flat that tds we can do without a configuration, especially fonts are an issue (why no tex/fonts/data/vendor/collection) $TEXMFCACHE is needed because distributers want control over the place where those files go; there is some default setup but ... Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------