Re: [PATCH] latest ash has broken 'echo' command
On Sun, Oct 24, 1999 at 04:51:07PM +0200, Marek Habersack wrote:
> * Herbert Xu said:
>
> > If you mean they use ash as /bin/sh and rely on features that are not part of
> But -n *IS* a part of POSIX! Unless you don't consider the optional parts of
> a standard, being part of the standard...
They are for the shell, but no for the shell scripts.
> > POSIX, they are on their own. If you mean they are writing #!/bin/ash
> > scripts, then I must say that they are very strange indeed.
>
> No, they are writing scripts which use optional features of a standard, that
> were always present in the implementations of the shell.
Do depend on an implementation of a shell, it either needs to be spelt out
somewhere like our policy, or they should use the right shell in the #! line.
I maintain that nobody writes #!/bin/ash scripts, so it does not matter if
ash changes its behaviour within the parameters set by POSIX assuming that
all #!/bin/sh are also within the parameters.
--
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: