Re: Bug#478850: posh: $ENV variable processed by non-interactive shells
On Thu, May 01, 2008 at 02:33:04PM +0100, Stephane Chazelas wrote:
> I don't really care about the "interactive" side of things
> ($ENV, $PSx, job control), but I tend to consider that for the
> scripting side of things, the optional features should be
> implemented. For instance, if you don't have command -v, there's
> no other reliable way to find out whether a command exists or
> not. So you have to have something (either "command -v" or
> "type").
If policy wants to mandate either "command -v" or "type", we could
conceivably move toward dropping "which" from debianutils.
Reply to: