Hello,
On Wed 25 Sep 2019 at 03:43PM +00, Dmitry Bogatov wrote:
>> 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.
Okay, so what we want to express here is the idea that there is an
exception for a package which uses a feature of systemd, where something
equivalent cannot be achieved by using a sysvinit script? Such as
something to access the systemd dbus interface.
I'm not sure how to express that right now, but I think it can be done.
--
Sean Whitton
Attachment:
signature.asc
Description: PGP signature