summaryrefslogtreecommitdiffstats
path: root/tags/p/possible-bashism-in-maintainer-script.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/p/possible-bashism-in-maintainer-script.tag')
-rw-r--r--tags/p/possible-bashism-in-maintainer-script.tag19
1 files changed, 19 insertions, 0 deletions
diff --git a/tags/p/possible-bashism-in-maintainer-script.tag b/tags/p/possible-bashism-in-maintainer-script.tag
new file mode 100644
index 0000000..e4644b0
--- /dev/null
+++ b/tags/p/possible-bashism-in-maintainer-script.tag
@@ -0,0 +1,19 @@
+Tag: possible-bashism-in-maintainer-script
+Severity: warning
+Check: shell/non-posix/bash-centric
+Explanation: This script is marked as running under <code>/bin/sh</code>, but it seems
+ to use a feature found in bash but not in the SUSv3 or POSIX shell
+ specification.
+ .
+ Some examples are:
+ .
+ - <code>==</code> in a test, it should use <code>=</code> instead
+ - <code>read</code> without a variable in the argument
+ - <code>function</code> to define a function
+ - <code>source</code> instead of <code>.</code>
+ - <code>. command args</code>, passing arguments to commands via <code>source</code> is not supported
+ - <code>{foo,bar}</code> instead of <code>foo bar</code>
+ - <code>[[ test ]]</code> instead of <code>[ test ]</code> (requires a Korn shell)
+ - <code>type</code> instead of <code>which</code> or <code>command -v</code>
+See-Also:
+ debian-policy 10.4