diff options
Diffstat (limited to 'dev-util/checkbashisms/files/checkbashisms-2.0.0.2-kill.patch')
| -rw-r--r-- | dev-util/checkbashisms/files/checkbashisms-2.0.0.2-kill.patch | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/dev-util/checkbashisms/files/checkbashisms-2.0.0.2-kill.patch b/dev-util/checkbashisms/files/checkbashisms-2.0.0.2-kill.patch deleted file mode 100644 index 7ddb94a5ae1a..000000000000 --- a/dev-util/checkbashisms/files/checkbashisms-2.0.0.2-kill.patch +++ /dev/null @@ -1,20 +0,0 @@ -`kill -HUP` is valid in POSIX - -we could extend the check to look for valid signal names, but that seems like -it's not worth the effort (when the # of signals is >30). if the code uses a -wrong signal name, then it'll hit a runtime error regardless of shell. - -https://sourceforge.net/p/checkbaskisms/checkbashisms/5/ -http://pubs.opengroup.org/onlinepubs/9699919799/utilities/kill.html -https://bugs.gentoo.org/458392 - ---- a/checkbashisms -+++ b/checkbashisms -@@ -496,7 +496,6 @@ - qr'\&>' => q<should be \>word 2\>&1>, - qr'(<\&|>\&)\s*((-|\d+)[^\s;|)}`&\\\\]|[^-\d\s]+(?<!\$)(?!\d))' => - q<should be \>word 2\>&1>, -- $LEADIN . qr'kill\s+-[^sl]\w*' => q<kill -[0-9] or -[A-Z]>, - $LEADIN . qr'trap\s+["\']?.*["\']?\s+.*[1-9]' => q<trap with signal numbers>, - $LEADIN . qr'trap\s+["\']?.*["\']?\s+.*ERR' => q<trap ERR>, - qr'\[\[(?!:)' => q<alternative test command ([[ foo ]] should be [ foo ])>, |