Date: Mon, 13 Jun 2005 11:08:08 +0200 From: Roman Neuhauser <neuhauser@sigpipe.cz> To: Dag-Erling Sm?rgrav <des@des.no> Cc: freebsd-ports@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: Bug in #! processing - "pear broken on current" Message-ID: <20050613090808.GB1789@isis.sigpipe.cz> In-Reply-To: <86psuuv1z6.fsf@xps.des.no> References: <200506090027.j590R2t0070899@repoman.freebsd.org> <20050609003619.GA10578@xor.obsecurity.org> <20050609100815.GB16677@over-yonder.net> <p06210258bece1422da20@[128.113.24.47]> <20050609160316.GC16677@over-yonder.net> <p06210259bece1ae26f44@[128.113.24.47]> <20050610062431.GA78875@isis.sigpipe.cz> <86fyvq3c4o.fsf@xps.des.no> <20050610112857.GB80719@isis.sigpipe.cz> <86psuuv1z6.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
# des@des.no / 2005-06-10 14:19:09 +0200:
> Roman Neuhauser <neuhauser@sigpipe.cz> writes:
> > That simply shows that all these *Linux* distros don't handle
> > shebang lines well.
>
> Actually, it shows that they handle shebang lines *correctly*, and
> that we don't unilaterally break Pear by aligning ourselves with them.
These two were identical before:
#!/usr/local/bin/php -n -q -dsafe_mode=0 -doutput_buffering=1
% /usr/local/bin/php -n -q -dsafe_mode=0 -doutput_buffering=1
These two are identical now:
#!/usr/local/bin/php -n -q -dsafe_mode=0 -doutput_buffering=1
% /usr/local/bin/php "-n -q -dsafe_mode=0 -doutput_buffering=1"
Obviously, "correct" is whatever behavior we declare as such.
But is the latter actually useful? The Linux distros you shown
hacking around the shebang parsing limitations (forking another
shell to achieve the correct parsing) shows just that: Linux distros
basically avoiding anything above the simplest "#!/bin/sh".
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050613090808.GB1789>