Re: SUSv3 + XSI => type (was: command -v in postinsts violating policy)
> Since SUSv3 is POSIX that should certainly be the basis of our policy.
> We should also support the XSI extensions since the ubiquitous set -e
> is defined as an XSI extension. As a consequence, we get the type command
> for free.
>
> I also do not oppose the adoption of the UP extensions since bash/pdksh
> is compliant AFAIK, and ash is only missing the history component of it.
Careful, XSI has a lot of bloat that has no business being in a shell.
If XSI extensions are to be mandated, it should be only in the context
of required builtins and such. Also, though XSI requires type be a
builtin, UP doesn't require that command be a builtin.
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: