[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#747320: marked as done (Mandate "type" and/or "command -v" in /bin/sh)

Your message dated Sun, 22 Jul 2018 15:52:47 +0800
with message-id <871sbvhflc.fsf@silentflame.com>
and subject line Re: Bug#747320: Mandate "type" in /bin/sh
has caused the Debian Bug report #747320,
regarding Mandate "type" and/or "command -v" in /bin/sh
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
747320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747320
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-policy
Version: 3.9.5.0

I came across this in /etc/init.d/exim4:

  OLDIFS="$IFS"
  IFS=:
  for p in $PATH; do
    if [ -x "$p/$UPEX4CONF" ]; then
      IFS="$OLDIFS"
      $p/$UPEX4CONF $UPEX4OPTS
      return 0
    fi
  done
  IFS="$OLDIFS"

I imagine that this kind of thing is found in many other places.

It seems to me that given that dash and bash both provide `type', and
the underlying functionality necessarily exists in the shell, it would
be better to mandate that the shell expose it.

I therefore propose that the following should be added to the list of
additional features listed in policy 10.4:

  * The XSI extension `type' must be supported .  It must exit
    zero iff the command is found.  The output format is not
    specified and scripts must not rely on it; scripts should
    rely only on the exit code using a construct such as
       if type foo >/dev/null 2>&1; then ...

Thanks,
Ian.

--- End Message ---
--- Begin Message --- 
Version: 4.1.5.0

On Mon 19 Mar 2018 at 02:46PM GMT, Simon McVittie wrote:

> It's also in SUSv4 (aka POSIX:2008) without any such qualifiers, so if
> #864615 is resolved with the suggested patch, command -v will implicitly
> be mandated by Policy (which would incidentally make sash a
> non-Policy-compliant choice for /bin/sh).

This is now indeed implicitly mandated.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: