On Wed, Sep 25, 2019 at 11:43 AM Dmitry Bogatov <kact...@disroot.org> wrote: > > > [2019-09-22 16:13] David Steele <ste...@debian.org> > > Candidate language attached. It adds "Also excepted are packages which > > require a > > feature of an alternate init system which is not available in SysV-Style > > init systems.". Thoughts? > > Imho, it opens loophole. Sysvinit does not provide equivalent of > sd_notify("SD_READY=1"), so any service that links to libsystemd for > that exactly call can be argued as "requiring feature [...] which is not > available [...]". > > As real life example I recall Avahi-related bug (can't find number right > now, sorry). Two inter-dependent services, where second fails to start > unless first is already ready to listen. > > I'd argue this is bug in design, but if we consider design is written in > stone, this is a bug in init.d script that must be worked around > somehow. > > With your change in place, avahi maintainers would be able to drop > sysvinit support instead of fixing init.d script. > > Very strong -1.
I'm just looking to avoid the scenario where I add systemctl calls to an init script, for a package that uses the systemd D-Bus interface. Alternate language is solicited.