Bug#497782: Re : Bug#497782: texlive-base-bin: latex compilation fails as "normal" user

[Frank Küster <frank@debian.org>]

Hi Jérôme,

nice that my hints solved your problem.  There's only one more thing I'd
like to learn:

"Jérôme Champavère" <jchampavere@gmail.com> wrote:

> jchampavere@jlaptop:~/these/avancement_2008$ env -i latex avancement.tex
> lstat(./latex) failed ...
> ./latex: No such file or directory
> This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)

I get a different result here:

$ env -i latex Pinball_Wizard.tex 
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)

Why does it find latex at all, on both system, when the environment
variable PATH is to be ignored? And if the shell parses the commandline
in advance and replaces "latex" by "/usr/bin/latex" internally, why does
Jérôme get the error message 

> lstat(./latex) failed ...
> ./latex: No such file or directory

And, just for curiosity, how can I see to what PATH is set when "env -i"
is used?

$ env -i echo $PATH 

gives


/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/home/frank/bin

because $PATH is substituted by the shell before env starts. If I
protect the variable from shell expansion, how can I make "someone" read
it again:

$ env -i eval echo '$PATH'
env: eval: No such file or directory

I guess Florent could answer this, but I haven't heard from him for ages.

Regards, Frank

-- 
Frank Küster
Debian Developer (TeXLive)
ADFC Miltenberg
B90/Grüne KV Miltenberg