- or setuptex should be rather an executable, that prints out the  environment to apply, then one would do something like this:  eval `setuptex`  (cleaner solution, but some work to do and all minimal-users must change  their habits...)

I theory adjusting PATH should do, but it's a nice proposal :) Mojca

On Thu, Jun 11, 2009 at 23:25, Peter Münster wrote:

On Thu, 11 Jun 2009, Mojca Miklavec wrote:

...

...

- or setuptex should be rather an executable, that prints out the  environment to apply, then one would do something like this:  eval `setuptex`  (cleaner solution, but some work to do and all minimal-users must change  their habits...)

I theory adjusting PATH should do, but it's a nice proposal :)

So TEXMFCACHE and TEXMFOS are not needed? And what about the praxis in contrast do the theory?

Here my little test: unset TEXMFOS unset TEXMFCACHE context test -> MTXrun | unknown script 'context.lua' or 'mtx-context.lua'

I left TEXMFCACHE variable as an excuse for not adding texmfcnf.lua to the distribution. (Though in theory it's still not needed, you just need to regenerate the database since LuaTeX doesn't know about the location of your old cache.) I have added the file now. I guess that TEXMFOS is not needed either. A month ago I decided to clean up setuptex a bit and removed everything but PATH setting ... and then the lack of TEXMFOS has destroyed the whole evening trying to figure out why it worked on everyone's machine but mine ... The bug has been fixed though, so ... if you update now to fetch that additional file ... does it work then? If yes, I'll remove the two remaining variables from setuptex. (I might be offline for a longer period though.) Mojca

On Fri, Jun 12, 2009 at 07:25, Peter Münster wrote:

On Fri, 12 Jun 2009, Mojca Miklavec wrote:

...

I left TEXMFCACHE variable as an excuse for not adding texmfcnf.lua to the distribution. (Though in theory it's still not needed, you just need to regenerate the database since LuaTeX doesn't know about the location of your old cache.)

I have added the file now.

Great, it works now. Clean solution!

But I'm asking myself, how SELFAUTOPARENT works: luatex is here: /opt/context/tex/texmf-linux-64/bin/luatex So it seems, that SELFAUTOPARENT is /opt/context/tex

Yes.

But I would have guessed that it's /opt/context/tex/texmf-linux-64 ...

No, that's SELFAUTODIR.

I even suggest, to suppress setuptex and only write in the readme/wiki, that the PATH must be adjusted so that context can be found, that's all.

We could issue a warning or we could put something at the end of first-setup.sh (that needs to be renamed anyway) to tell users that they should either adjust path or use the script. I might be having weird habits, but I really like being able to have a simple single command that switches the TeX tree. export PATH=/something/very/long/:$PATH costs more effort to type than just ". setuptex" :) :) :) Wiki could/should be modified for sure. One day I need to revise all kinds of instructions for different installations ... (finishing study in time has a high priority at the moment). The initial idea of setuptex was to shield all the environmental variables that have been set by tetex. I suspect that cleaning up setuptex had a consequence that it's not able to shield tetex any more, but nobody has complained so far ... Mojca