Re: Proposed new POSIX sh policy, version two
On Sat, Nov 25, 2006 at 03:54:05PM +0200, Jari Aalto wrote:
> > Maybe bash should restrict its features when called sh... like gzip
> > changes its features when called gunzip, etc.
> I think this would complicate the bash's C-code base unnecessarily.
> The problem is not in the bash, but in the symlink. The proper way
> would be to ship in etch+1
> /bin/sh -> /bin/dash
Er, what's *proper* about this? It is precisely /bin/sh that is the most
"essential" feature of the bash package; there might be room for discussion
on whether we should consider /bin/bash to be outside of the essential
feature set, but now you're talking about a change that requires adding dash
to the set of essential packages *in addition to* bash, with no explanation
of why this is appropriate.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/
Reply to:
- References:
- Re: Proposed new POSIX sh policy, version two
- From: Thomas Bushnell BSG <tb@becket.net>
- Re: Proposed new POSIX sh policy, version two
- From: Jari Aalto <jari.aalto@cante.net>
- Re: Proposed new POSIX sh policy, version two
- From: Thomas Bushnell BSG <tb@becket.net>
- Re: Proposed new POSIX sh policy, version two
- From: David Weinehall <tao@debian.org>
- Re: Proposed new POSIX sh policy, version two
- From: Thomas Bushnell BSG <tb@becket.net>
- Re: Proposed new POSIX sh policy, version two
- From: Jari Aalto <jari.aalto@cante.net>
- Re: Proposed new POSIX sh policy, version two
- From: Thomas Bushnell BSG <tb@becket.net>
- Re: Proposed new POSIX sh policy, version two
- From: Jari Aalto <jari.aalto@cante.net>
- Re: Proposed new POSIX sh policy, version two
- From: Mike Hommey <mh@glandium.org>
- Re: Proposed new POSIX sh policy, version two
- From: Jari Aalto <jari.aalto@cante.net>