Re: Bug#270868: Should not implement "test" builtin
> Policy clause 10.4 is aimed at preventing that situation -- at
> regulating scripts in such a way that it is possible for the
> administrator to point /bin/sh at something faster than bash and thereby
> to make some scripts run faster -- but its language isn't adequate to
> the task. It tells script authors to avoid writing scripts that use
> "#!/bin/sh" and that use extra-POSIX features of shell builtins.
> However, "echo" isn't a shell builtin; therefore 10.4 doesn't restrict
> how it can be used.
Odd, then, that 10.4 explicitly mentions "echo".
> Now someone who hasn't read the whole thread is going to think that 10.4
> should be extended to cover all POSIX utilities. We can send that
> person back to the beginning of the "Bug#267142: debian-policy: Sections
> 10.4 and 6.1 are inconsistent" thread where it is pointed out that this
> measure would not suffice because shells can build in commands other
> than ones mentioned by POSIX.
Shells do do this. I don't understand how that's relevant.
> The latter is off topic for the "Bug#270868: Should not implement 'test'
> builtin" thread. The argument I made there is simply that posh is
> enforcing the use of an impoverished "test" command for no good reason.
What would be a good reason to enforce the use of an "impoverished
'test'"?
Reply to: