Re: [PATCH] latest ash has broken 'echo' command
On Oct 21, Sven Rudolph wrote:
> Herbert Xu <herbert@gondor.apana.org.au> writes:
>
> > On Thu, Oct 21, 1999 at 03:04:07PM +0200, Marek Habersack wrote:
> > > The latest ash package (0.3.5-7) has a broken 'echo' builtin
> > > implementation.
>
> > It's not broken. The Single Unix Specification says that echo must not
> > support any options. The kernel makefile should be fixed.
>
> Did we decide to follow Single Unix Specification. I thought we were
> on POSIX, and my draft allows -n (implementation defined).
>
> According to rationale this compromise fulfills BSD and SYSV
> tradition.
>
> The Single Unix Specification explicitely forbids BSD heritage while
> it standardises the SYSV way.
>
> Following the free software tradition insisting on the Single Unix
> Specification seems to be a bad choice.
Perhaps compliance with the SUS should be an option within Debian (for
example, many GNU utilities accept $POSIXLY_CORRECT; maybe we should
implement $SUS_CORRECT where applicable). I can see environments
where compliance with SUS may be necessary in the future (for example,
if it were adopted as a government purchasing standard, like POSIX [or
a close cousin thereof] is today).
Chris
--
=============================================================================
| Chris Lawrence | Visit my home page! |
| <quango@watervalley.net> | http://www.lordsutch.com/chris/ |
| | |
| Debian Developer | Visit the Lurker's Guide to Babylon 5: |
| http://www.debian.org/ | <*> http://www.midwinter.com/lurk/ <*> |
=============================================================================
Reply to: