Package: debian-policy Version: 3.7.3.0 Severity: minor Quoting a portion of the current section 10.4: > Scripts may assume that /bin/sh implements the SUSv3 Shell Command > Language[62] plus the following additional features not mandated by > SUSv3:[63]
Based on the results from the last archive-wide checkbashisms check on i386, the situation is as follows: There are about *91* unique binary packages with at least one match for the trap with signal numbers check. And about *112* unique binary packages with at least one match for the 'kill -[0-9] or -[A-Z]' check. Both checks are meant to detect the usage of the widely used XSI extensions for kill and trap as documented in [1] and [2] respectively. Message <[EMAIL PROTECTED]>[3] describes my opinion about the subject which is resumed to the following: > so we either > request policy to require kill|trap -SIGN and kill|trap -[0-9] or we > annoy the maintainers of those 179 packages. (179 was the number of the affected packages based on an archive wide check on the amd64 packages). As it seems lots of people have agreed on using those XSI extensions IMHO the policy should be updated to permit the usage of the XSI extensions for the trap and kill built-ins as described in the SUSv3 Shell Command Language in /bin/sh scripts. [1]http://www.opengroup.org/onlinepubs/009695399/utilities/kill.html [2]http://www.opengroup.org/onlinepubs/009695399/utilities/trap.html [3]http://article.gmane.org/gmane.linux.debian.devel.policy/9779 Kind regards, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html
signature.asc
Description: This is a digitally signed message part.