Taco Hoekwater wrote:
Please note this implementation logic is not set in stone yet. We preferred to start as simple as possible, but extensions may be needed. (currently we have a "works for me" system). Keep in mind that if your installation is really outlandish, you can just set TEXMFCNF in the environment explicitly.
an additional note: it is important to keep in mind that when you don't set TEXMFCNF and TEXMF, ther eis a potential clash with existing tex installations; the main reason for having setuptex in the minimals is that it permits many parallel installations (users like taco and me often have many 'independent' istallations (for projects) so, if the automatisms fail (i.e. you don't set TEXMF and TEXMFCNF yourself and depend on luatools cum suis to figure out where the configureations are) there is probably some interference with environment variables; i.e. when you for instance install tetex (or when the system came with it) you can be pretty sure that some variables are set and cf tds/kpse environment variables take precedence); in that case there is no way around overriding them at the shell level (as setuptex does) this also means that when you install the minimals allongside an existing tex installation, you probably still need to use setuptex
All such files will be read before any of the texmf.cnfs, and so they can be used to overrule texmf.cnf values, TEXMFCACHE in particular. The lua script has to return a table. Mine (I have only one) looks like this:
config = {} config.TEXMFCACHE = "/tmp" return config
there is an example contextcnf.lua file in the distribution that will have the variables that we support in addition to the normal ones in texmf.cnf ( 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 -----------------------------------------------------------------