Re: [PATCH] latest ash has broken 'echo' command
On Fri, Oct 22, 1999 at 02:22:21PM +1000, Herbert Xu wrote:
> Michael Stone <mstone@debian.org> wrote:
> > 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:
Again, what's your point? If a script doesn't behave properly it's a bug
against the script. But you're not doing users a service by breaking
things because you think they're wrong. Ash had a behavior. Its behavior
was not in violation of policy. Scripts that used the functionality ash
provided may have been in violation--but localally-grown scripts aren't
governed by policy. So you broke things in order to force ideological
purity, broke debian *and non-debian* scripts, changed the behavior of a
policy-compliant program without warning, and what did you gain?
Mike Stone
Reply to: