Re: [PATCH] latest ash has broken 'echo' command

[David Benson <daveb@idealab.com>]

> > Of course I'm going back the scripts, AFAIK nobody actually writes ash
> > scripts.  So the only significant use of ash on Debian is as /bin/sh.  Now
> > 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 (at the moment anyway, someone mentioned that we can
> > get POSIX changed, maybe you guys should start lobbying now).  So either
> Someone else said that POSIX 1003.1e allows arguments and parameters, so we
> need to have someone who has the Part II of the standard. Anyone?

I'm rather sorry to continue dragging this out,
but now and then I actually write startup scripts
so this is relevant...

Is it fair to assume that /bin/echo -n and /bin/echo -e will
always work?  
[What else *can* you do if /usr isn't necessarily available?]

If so, patches won't be very hard to make, nor very objectionable
to the real maintainers.  Indeed a massive grep could turn them all
up fairly effectively.

Then the only annoyances are the non-debian shell scripts already in use.
Sigh...


- Dave