Nikolai Weibull wrote:

* Hans Hagen [Nov 01, 2004 13:55]:

...

...

Exactly what do I need to do after running setuptex, mktexlsr, and texexec --make --alone? PATH needs permanent updating for sure, but what else? texexec won't work (kpsewhich won't work) unless setuptex is sourced before I try running it in a fresh shell. What am I missing in my setup?

...

you can add the call to setuptex to your local profile

...

. /path-to/setuptex /path-to

Sure, but what variables are actually necessary to export and, more interestingly, why are they needed in the environment at all? When running from tetex everything works fine. I'm guessing this is mostly due to differences between stuff in tetex 2.0.2 and more recent releases of software, but I still can't see why it would be necessary to fill the environment with some 10-20 variables. nikolai (the environmentalist)

setuptex exports the variables for you; if you look in that file, you can see that i define all critical variables the problem with tetex (last time i installed it) is that it sets paths and other things in ways that make parallel distributions painful; also, i dislike sorting out all kind of unexpected side effects due to settings of texinput paths, home directory stuff, texmf.cnf files not being in theirnatural place (it seems that some unix distributions prefer the etc path) so, the idea of setuptex is that you can have tetex and anytex on your system and still use a minimal context which, when setuptex is ran, is completely isolated (al also add some more trees, like texmf-project, texmf-fonts which are not set by other tes distributions) 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 -----------------------------------------------------------------

Henning Hraban Ramm wrote:

Am 01.11.2004 um 15:39 schrieb Hans Hagen: Strangely it doesn't (at least on MacOS X). I know shell scripts and I had to adapt it to MacOS X a bit; the variables are defined in the script, but don't get exported!

are you sure, you are using bash _and_ you have used the command '.'? This command evaluates the given script in the context of the running shell. If you only run the script, it gets its own subshell and the variables are set (and exported) in this subshell but not in the calling shell! Uwe -- voiceINTERconnect www.voiceinterconnect.de ... smart speech applications from germany