Re: [PATCH] latest ash has broken 'echo' command
Marek Habersack <grendel@vip.net.pl> wrote:
>
> * Herbert Xu said:
>> The thing is even POSIX allows this behaviour if I read Sven's message
>> correctly. The options are strictly implementation defined, so that means
>> you cannot rely on them in a portable script.
> You are still going back to the script matter, but we are talking about the
> shell, *not* the scripts! Shell should, more, it HAS to provide all the
> expected features. That's IMHO, of course.
Of course I'm going back the scripts, AFAIK nobody actually writes ash
scripts. So the only significant use of ash on Debian is as /bin/sh. Now
we have a policy that requires #!/bin/sh scripts to be POSIX compliant so
that this can happen. Problem is that we've got too many scripts which
just aren't compliant (at the moment anyway, someone mentioned that we can
get POSIX changed, maybe you guys should start lobbying now). So either
we change the policy in which case I'll probably fork ash into two binaries
with one designed to be strict and the other one suitable as a /bin/sh, or
we'll have to start fixing scripts.
It was foolish me to do this change so close to the freeze, that is why I've
reverted to the old behaviour in 0.3.5-8. However, once potato is released,
we'll still have to deal with this issue.
--
Debian GNU/Linux 2.1 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Reply to: