From b5624495afec0a13d169c245362e945ce27d97a8 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Thu, 2 Jan 2014 17:20:47 +0000 Subject: [PATCH] 727708: my draft resolution: permit maintainers to object to raise(SIGSTOP) --- 727708_initsystem/draft-resolution-iwj.txt | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/727708_initsystem/draft-resolution-iwj.txt b/727708_initsystem/draft-resolution-iwj.txt index 72a3a6e..a56252d 100644 --- a/727708_initsystem/draft-resolution-iwj.txt +++ b/727708_initsystem/draft-resolution-iwj.txt @@ -73,8 +73,10 @@ Support requirements for packages: C. However, a maintainer is entitled to consider a patch unreasonable if it: (i) Requires additional build-dependencies; or - (ii) Requires additional runtime dependencies except lsb-base; or - (iii) Introduces other than trivial new code into the daemon. + (ii) Requires additional runtime dependencies except sysv-rc; or + (iii) Introduces other than trivial new code into the daemon; or + (iv) "Abuses" SIGSTOP as done by the upstart "expect stop" + protocol and as disliked by the systemd community. Code to write to an already-open fd and close it, or to raise a signal, will usually be trivial for these purposes. (This includes @@ -84,10 +86,16 @@ Support requirements for packages: socket and send a message will not usually be considered trivial. We are aware that at present it is not possible to provide a patch - for systemd's main non-forking daemon startup readiness protocol - which is necessarily reasonable by this definition. If the systemd - community in Debian wants the widest adoption in the project, this - should be addressed by changes to the systemd package. + for any of systemd's or upstart's main non-forking daemon startup + readiness protocols which is necessarily reasonable by this + definition. + + Therefore if the upstart and systemd communities in Debian want the + widest adoption in the project, these problems should be addressed + by changes to the upstart and systemd package to widen their + support for different startup protocols. Ideally each init should + in any case provide support for the main protocols supported by + their competition. Failure to apply reasonable patches, including failure to explain promptly and constructively why a patch is not reasonable, is -- 2.39.5