Bug in #! processing - "pear broken on current"
Florent Thoumie
flz at xbsd.org
Fri Jun 10 08:06:58 GMT 2005
On Jun 10, 2005, at 8:24 AM, Roman Neuhauser wrote:
> # gad at FreeBSD.org / 2005-06-09 12:37:20 -0400:
>
>> [moved over from the thread:
>> Re: cvs commit: src/sys/kern imgact_shell.c
>> on the cvs-src mailing list...]
>>
>> At 11:03 AM -0500 6/9/05, Matthew D. Fuller wrote:
>>
>>>
>>> Well, I dunno what part of it is giving troubles (and I haven't seen
>>> it myself, since I'm still on RELENG_5 for the moment; just
>>> keeping my
>>> eyes open). It doesn't seem like a terribly esoteric line though:
>>>
>>> #!/usr/local/bin/php -n -q -dsafe_mode=0 -doutput_buffering=1
>>>
>>
>> It is very likely that the problem which is being seen with this
>> script is due to the change in parsing I committed on May 28th.
>> Before the change, php would have been started up with:
>>
>> [0] -> /usr/local/bin/php
>> [1] -> -n
>> [2] -> -q
>> [3] -> -dsafe_mode=0
>> [4] -> -doutput_buffering=1
>> [5] -> /usr/local/bin/name-of-script
>> [6...] -> parameters specified by user
>>
>> and now php is being started with:
>>
>> [0] -> /usr/local/bin/php
>> [1] -> -n -q -dsafe_mode=0 -doutput_buffering=1
>> [2] -> /usr/local/bin/name-of-script
>> [3...] -> parameters specified by user
>>
>> Assuming 'php' does not know what to do when all those options are
>> glommed together in a single argument, then the above script would
>> not work right on any other operating systems either. The change
>> I made on the 28th gets FreeBSD to work more like other OS's when
>> it comes to parsing that #!-line in scripts.
>>
>
> The pear people have hacked around the other OS's limitations.
>
> This change makes FreeBSD lose one small but fine competitive
> advantage over other unix-like systems. Pity.
FreeBSD needed special handling, no it doesn't anymore.
I'm not sure that's losing a *competitive* advantage.
--
Florent Thoumie
flz at xbsd.org
More information about the freebsd-ports
mailing list