Re: [gentoo-dev] /{"", usr/}bin path changed. What is the right solution for scripts?

[Peter Volkov]

On Sun, 2007-04-01 at 16:21 +0100, Ciaran McCreesh wrote:
> env not being in /usr/bin will break an awful lot of stuff. It's listed
> in many textbooks as being the safe way of doing things.

On Sun, 2007-04-01 at 08:46 -0700, Alec Warner wrote:
> However using env really only makes sense in the
>
> #!/usr/bin/env foo
>
> case.  Pretty much every other case you should be setting PATH to
> something proper in your script.

Thank you for remarks.

BTW. Looking into sources I found that env itself does not have default
PATH but calls execvp () which have VERY reduced PATH=":/bin:/usr/bin" .

command -p by default in bash uses the following
PATH /bin:/usr/bin:/sbin:/usr/sbin:/etc:/usr/etc

So I think as there is no standard on what is the default PATH the most
viable solution is to set default PATH in the script itself.

-- 
Peter.