Le 16 mai 06 à 01:14, Hans Hagen a écrit :

Maurice Diamantini wrote:nment.

...

Usually, one can build dynamicaly (default) variable environment at the start of a programm (i.e. in the same process and sub-process), then let the original environment untouch while ending the programm.

this is what

texmfstart --tree=.... texexec ....

does; it sets env vars specified in either setuptex.tmf in the path mentioned as tree, or some specific tmf file; those tmf files are platform independent. this is how i run multiple (different trees) on one machine (say a web server);

Thank you very much. So I can do a little "texexec" script, add its path in front of the global path (so that it will be found before any standard old ConTeXt distrib) and use the new "texexec" shell script as the main context executable as usualy. The main avantage over my previous proposal is that it doesn't even require adding a new path in the PATH environment variable (which already is quite accectable!).

...

I don't know much about context, but if you use some texmfstart laucher, it could have the responsability of that job). In fact, I'd like to only have to add some PATH for using a personnal full ConTeXt distribution near another standard LaTeX (containing obolate Context) this is what in regular distributions texmf-local is for

Yes, but the texmf-local is part of a particular directory from a particular network or host. And I like to separate my own (full, independant, robust, ...) ConTeXt environmement from the several LaTeX distrib I use (e.g. my unix/osX account is mirror via rsync between hom, work, and another network.

...

LaTeX will probably become again my main xTeX environment, but I'd like to be able to switch ponctualy to a recent ConTeXt distro, without hacking and breaking my main TeX environment. in that case, just put the latest context in your main tree (unzip cont-tmf in texmf-local or so); that should work as always

No, because of recent font (lm) probleme, I decided to keep a full context distrib (linuxtex.zip + macosxtex.zip + justtex.zip) in my personnal home directory. I positionned this environment with some "setuptex" variante before using context program (with all previous problems when comming back to LaTeX)

...

Because the Makefile should work on all plateform (and in a year or two also if possible!) I use only the standard texexec (instead of texmfstart and path argument). But if you say texmfstart become the standard way: I'd switch to! well, you can still use texexec.rb instead of texexec.pl and avoid texmfstart; it's just that then you need to keep an eye on when texexec changes

Do you mean that "texexec.rb" is clever enought to guess its ows directory tree ? Great, that what I asked for ;-) (and if "texexec.rb"" becomme the standard texexec tool the problem is solved (no more need to do a small texexec" shell script) but... ... for context programme only, but what about other tools (metapost, mp2pdf...)

...

Just a remark in that case: texmfstart seems a bad name, bacause not related to "ConTeXt" Why not simply "context" or "ctx" as the main ConTeXt tool?) because i use it to run anything organized in a tree (e.g. xsltproc); running context progies i just part of the game

Ok, I can always make an alias "ctx" for "texmfstart --tree=..." alias ctx=texmfstart --tree=/home/myHome/myLocl/fullcontext perhaps it solves all problem at a time! I'll try that in the next two week. Thank you very much, Maurice