Re: Starting /bin/sh in output configure file

[Russ Allbery]

R0b0t1 <address@hidden> writes:

> A hardcoded binary path isn't portable, the correct solution is to use
> `env sh`. Typically this is seen as:

> #!/usr/bin/env sh

> Which technically causes the same problem Mr. Akhlagi was
> experiencing, but on most desktop Unixes the location of `env` is more
> predictable than the location of various interpreters.

I am extremely dubious that the location of env is more predictable than
/bin/sh.  python or perl or whatnot, yes, but not /bin/sh, which is
probably the most hard-coded path in UNIX.

But more to the point for this specific request, it would surprise me a
good deal if Android would move sh and not also move env to some other
directory than /usr/bin.  If you're going to break compatibility that
much, it's unlikely you're going to keep compatibility for env.  But,
well, I've been surprised before....

-- 
Russ Allbery (address@hidden)              <http://www.eyrie.org/~eagle/>