However, more to the point, is the sarge debian treatment of tetex for environment variables consistent with what I might discover in docs in CTAN or wherever official TeX info comes from. If so, then no problem. I don't have the time right now to investigate what the behavior should be (and don't remember off the top of my head). For info purposes, the only *other* ones that were set that caused the behavior in the bug report are TEXMFCNF and TEXMF. You might test them if unsure about their behavior in the current version. They are set on my iBook which still has woody on it and it works fine. Also I suspect that they are set in my acct on my machine at school which is running Mandrake 10.0 and everything works okay there.
Hope this info helps, jeff
On Mar 1, 2005, at 2:25 AM, Frank Küster wrote:
"Jeffrey B. Green" <[EMAIL PROTECTED]> schrieb:
Sent this bug in this morning, however during the day at work I thought that the environment variables that were working from woody might be the problem. So I commented all pertinent to tetex out except for TEXINPUTS and voila, it worked. Before you close out this bug report, you might put in some test for the correct environment variable settings in your tetex debconfig.
Ah, this is interesting. You are the second one who has such problems
because of environment variables that were set on woody. However, I
never needed to set any environment variables to get tetex to work in
woody, and I also don't know where this is recommended. Do you remember
why you had to set those variables, or which documentation made you
believe that it should be done? We should probably also fix this.
Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
