On 07/15/2010 06:53 PM, Russ Allbery wrote:
"Giacomo A. Catenazzi"<c...@debian.org> writes:
As we have in "test" item, I think we should add ",if implemented as a
shell built-in," also for the kill command.
Good point. Here's a new patch. (This doesn't apply to trap because I
don't think trap can work without having it implemented as a shell
built-in.)
diff --git a/policy.sgml b/policy.sgml
index 6c770fd..d694fd2 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7460,7 +7460,19 @@ fname () {
</example>
must be supported and must set the value of<tt>c</tt> to
<tt>delta</tt>.
-</item>
+ </item>
+ <item>The XSI extension to<prgn>kill</prgn> allowing<tt>kill
+ -<var>signal</var></tt>, where<var>signal</var> is either
+ the name of a signal or one of the numeric signals listed in
+ the XSI extension (0, 1, 2, 3, 6, 9, 14, and 15), must be
+ supported if<prgn>kill</prgn> is implemented as a shell
+ built-in.
+ </item>
+ <item>The XSI extension to<prgn>trap</prgn> allowing numeric
+ signals must be supported. In addition to the signal
+ numbers listed in the extension, which are the same as for
+ <prgn>kill<prgn> above, 13 (SIGPIPE) must be allowed.
+ </item>
</list>
If a shell script requires non-SUSv3 features from the shell
interpreter other than those listed above, the appropriate shell
Thanks,
seconded.
ciao
cate
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c3f3fd8.2090...@debian.org
