Also mention that the Files pattern syntax is the same as fnmatch(3)
and GNU find -path without [] patterns. Thanks, Jonathan Nieder and
Ben Finney.
+ * Suggest checkbashisms from devscripts or the posh shell for checking
+ whether /bin/sh scripts are Policy-compliant rather than recommending
+ dash. Thanks, Raphael Geissert. (Closes: #490604)
* Install the HTML version of upgrading-checklist in the policy.html
directory as upgrading-checklist.html so that it can be deployed on
www.debian.org in a way that will allow links to Policy sections to
<p>
You may wish to restrict your script to SUSv3 features plus the
above set when possible so that it may use <file>/bin/sh</file>
- as its interpreter. If your script works with <prgn>dash</prgn>
- (originally called <prgn>ash</prgn>), it probably complies with
- the above requirements, but if you are in doubt, use
- <file>/bin/bash</file>.
+ as its interpreter. Checking your script
+ with <prgn>checkbashisms</prgn> from
+ the <package>devscripts</package> package or running your script
+ with <prgn>posh</prgn> may help uncover violations of the above
+ requirements. If in doubt whether a script complies with these
+ requirements, use <file>/bin/bash</file>.
</p>
<p>