Re: [PATCH] latest ash has broken 'echo' command
Herbert Xu <email@example.com> writes:
> Well my point is that (after potato is released) we should either change
> the policy because *so many* scripts break it as it now stands, or fix all
> those scripts (that's going to be monumental) in which case the change in ash
> would not matter.
Last option prefered. Potential problem: Some /etc/init.d/ scripts
might be conffiles, so they won't be upgraded if the user preserves
his locally-hacked version.
> The fact of the matter for ash is, do we want it to be a shell that can only
> run POSIX compliant scripts (defined as scripts that can execute with all
> POSIX compliant shells), or do we want it to be a shell that includes all
> the optional features allowed by POSIX so that it can run shell scripts
> that aren't POSIX compliant?
If we wanted the latter we'd use bash ;-)
Sven Rudolph <firstname.lastname@example.org> http://www.sax.de/~sr1/