Re: [PATCH] latest ash has broken 'echo' command
On Mon, Oct 25, 1999 at 11:44:38AM +0200, Marek Habersack wrote:
>
> You keep repeating this argument, but so far you haven't presented us the
> relevant fragment of the standard that specifically forbids the behavior.
OK, this is the last time that I'll spell it out to you. I'm in this debate
because I maintain a package called ash. That package exists for the sole
purpose of acting as /bin/sh. That is only possible if all #!/bin/sh scripts
were restricted by some standard. This currently happens to be POSIX.
So for me, either those scripts have to be fixed to comply with the policy,
or the policy must be changed to note this exception.
> > True, exiting for -n is probably within the parameters. But remember we're
> > trying to catch -e as well.
>
> -e is not even in half that common as -n, so it's not a big deal to get rid
> of all the -e's from the scripts that actually use it.
Well they happen to be in the same boat as far as POSIX compliant scripts
go.
--
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: