Hello, On Sun 21 Jul 2019 at 08:46PM -04, David Steele wrote: > In section 9.11 (The Operating System/Alternate init systems), it is > stated that "...any package integrating with other init systems must > also be backwards-compatible with sysvinit by providing a SysV-style > init script...". There is a single exception for the alternate init > system implementation itself. > > There are other exception conditions that we may want to consider > here. For instance, if a package has an explicit dependency on a > particular "alternate" init system, to, say, access the systemd D-Bus > interface, there is likely little value in providing sysv init > scripts. > > I suggest that something like the following line be added to the end > of the second paragraph in that section: > > "Also, SysV-style init scripts may be omitted for packages which have > an explicit dependency on an alternate init system." People who don't like systemd have been working to provide replacements for these hard dependencies. E.g. there is elogind so that packages which depend on logind can work on a sysvinit system. We would want to be careful to word this requirement such that it did not license maintainers to do things which block the work of those who don't like systemd. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature