Re: [PATCH] latest ash has broken 'echo' command
Michael Stone <mstone@debian.org> wrote:
> On Fri, Oct 22, 1999 at 09:19:41AM +1000, Herbert Xu wrote:
>> 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.
> What's your point? Who cares if people can rely on them for a portable
> script--they just want the behavior they had last week. We're building a
> distribution, not an ivory tower.
Because of this bit in our policy:
The standard shell interpreter ``/bin/sh'' may be a symbolic link to
any POSIX compatible shell. Thus, shell scripts specifying ``/bin/sh''
as interpreter may only use POSIX features. If a script requires
non-POSIX features from the shell interpreter, the appropriate shell
has to be specified in the first line of the script (e.g.,
``#!/bin/bash'') and the package has to depend on the package
providing the shell (unless the shell package is marked `Essential',
e.g., in the case of `bash').
Of course there is no time to do anything about this for potato. So
let's all sit on it until potato is released.
--
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: