Re: Bug#344269: etch release policy: scripts "must" set "appropriate" #! line?
On Thu, Jun 22, 2006 at 04:30:39PM +0200, Frank K?ster wrote:
> Russ Allbery <firstname.lastname@example.org> wrote:
> > I thought Steve followed up and said that yes, they're unacceptable,
> I didn't find any answer, neither in may mailbox, on debian-release, nor
> in the bug log.
There were two anwers, from me and Steve:
Your original post was not mentionning any bug number by the way.
> > because that script magic relies on the script being run by a shell
> > (something I hadn't realized until he pointed it out). If you try to run
> > a binary that starts with the above and no #! line via, say, execv inside
> > a C program, it will fail. It only works from the command line because
> > the shell falls back on trying to interpret binaries with no valid magic
> > as shell scripts.
Well, as I explained, it does not really work from the command line either
because you might be using tcsh and the script might be in POSIX sh and
tcsh will not parse it.
The only case where it reliably works is when the script is always
called from another script with a proper #! in the same language. In my
opinion adding a #! line is easier that deciding whether this condition
is reliably met.
Imagine a large red swirl here.