Hi,
Jakub Wilk wrote:
[...]
checkbashisms considers `kill -9` as a bashism:
$ echo "#!/bin/sh" > tmp
$ echo "kill -9 foo" >> tmp
$ checkbashisms tmp
possible bashism in tmp line 2 (kill -[0-9] or -[A-Z]):
kill -9 foo
Actually, according to POSIX, such a usage is perfectly valid:
POSIX itself requires only -s and -l to work; -SIGNAME and -SIGNUMBER are
XSI extensions - see
http://www.opengroup.org/onlinepubs/000095399/utilities/kill.html
XSI extensions are not part of the base POSIX specification, which is what
policy requires; checkbashisms (and the lintian checks from which it was
originally derived) is based on a definition of bashism that roughly equates
to "behaviour that a Debian policy compliant shell script can not rely on".
There is a request open against policy (#477240) to allow the use of the XSI
extension for kill and trap; until that's approved, checkbashisms is
unlikely to change in that respect.
(Ideally it would have the capability to highlight those issues which are
XSI extensions, UP extensions, etc. That's a longer-term goal though)
Regards,
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
