Re: environment variable

 first thanks for all answers!

 >
 > I recommend not to modify latex macros like \usepackage or \input at
 > all, it certainly will lead to confusion in the future.
 >
 > There is no good reason to use env-vars in (la)tex.
 >
 > The most straightforward way in teTeX-3 is to put user files into
 > $TEXMFHOME, which usually is $HOME/texmf.
 >
 > Reinhard
 >


 Here is one example why we want the flexibility of using $HOME in our documents:

 #####
 user1 is working on part-x of a machine 'a', the calculating system produce in
$HOME/machine-a/part-xy/part-x lots of files from calculations etc. and also
latex-files automatically. This user1 can also add some description to these
latex-files manually

 user2 is working on the same machine 'a' but on part-y, so he has also several
files in $HOME/machine-a/part-xy/part-y

 when both users are ready, both will checkin with CVS (Concurrent Versions
System) their files and also their latex stuff !

 NOTE: When one of them wants to create a report on machine-a/part-xy, he will
need from part-x and part-y all latex-files from the other user/users.
 He (this user) will do an update in $HOME/machine-a/part-xy and should get all
files which user1 and user2 produced and cheked into CVS.

 because he used the $HOME env-variable in the latex -files he is now able to
produce the report(s) for machine 'a' !
 #####

 we cannot move all latex-files in $HOME/texmf, we have here about 10 machines,
one machine has about 12000 parts! ... with 100 GB data, all under control of CVS

 I would prefer not to change our system now, it's too much work!

 so if we cannot work with $HOME in tetex-3, we must go back to tetex-2 and stay
on this version?

i hope it is now more clear why we want this easy way of using $HOME in latex.


thx

Olli