Bug#267142: debian-policy: Sections 10.4 and 6.1 are inconsistent (Posix doesn't say what you think it says)
> Yes. Have you read my original bug report, which goes into
> considerable detail? I'm not interested in rehearsing the whole thing
> in response to one-liner questions.
Yes. You may note that I replied directly to your original bug report.
> If a maintainer finds a big in dash, and it's a pain to work around,
> it's a simple matter to just #!/bin/bash and be done with it.
Actually, what usually happens is that a bug is filed against dash and
Herbert fixes it.
> This is incorrect.
No.
> Policy requires restriction to Posix-specified shell features. "test"
> is not a shell feature according to Posix.
POSIX mentions "test" both as a Korn shell builtin and as a Bourne shell
builtin.
> On the other hand, if you say "Posix allows test to be builtin,
> therefore it is a shell feature", then the consequences are horrible,
> because Posix allows *anything whatsoever* to be builtin, including
> say "debconf", and for a command like "debconf" the builtin could do
> *anything whatsoever*.
>
> So that second interpretation is clearly not correct. Thus the former
> one is.
This is incorrect.
"debconf" is not specified by POSIX. A #!/bin/sh maintainer script
calling "debconf" does not suddenly violate policy if bash implements a
"debconf" builtin. Nor does bash violate policy by doing so.
How does one interpret policy to make any of the preceding three
statements untrue?
Reply to: