Re: [PATCH] latest ash has broken 'echo' command
Hi,
>>"Herbert" == Herbert Xu <herbert@gondor.apana.org.au> writes:
>> > 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
>>
>> But the fact that scripts aren't compliant does not mean that the shell
>> should break them even more,
Herbert> Well the fact is that if ash has to support features that
Herbert> are not required by POSIX (but are compatible with it), just
Herbert> where do you draw the line?
With a modicum of common sense? Like you choose POSIX
compatible non-mandatory extensions based on how common the usage is?
Be somewhat flexible in what you accept?
Or are you delibrately trying to get ash deprecated as an
/bin/sh candidate?
Herbert> Many bashisms belong to this category. Pretty soon ash will
Herbert> become bash.
If minimalism means that ash is not cencerned with giving the
least bit for quality of implementation issues, I'd rather it became
more like bash, then mostly unusable.
manoj
--
Never give an inch!
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: