Bug#932704: debian-policy: Don't force sysvinit compatibility if e.g. alternate init required

[Sean Whitton <spwhitton@spwhitton.name>]

Hello David,

On Sun 29 Sep 2019 at 10:35AM -04, David Steele wrote:

> On Sat, Sep 28, 2019 at 1:05 PM Sean Whitton <spwhitton@spwhitton.name> wrote:
>>
>> Hello,
>>
>> On Sat 28 Sep 2019 at 04:18PM +00, Dmitry Bogatov wrote:
>>
>> > Reasonable. Then let's drop part about Depends:
>> >
>> >       [ ... All packages with daemons must provide init.d scripts ...],
>> >       unless software is only usable, by upstream's design, when
>> >       pid1 is provided by some other init system.
>>
>> I think this would work.  What do you think, David?
>
> I don't know. It provides more clarity the original Policy question, but raises
> a technical one I don't know the answer to. For my special case, is it
> practical to use systemd (via D-Bus) to manage system daemon
> start/stop when it is
> not pid1? If yes, things may have gotten worse (I'm responsible for getting this
> all to work correctly?).

Unfortunately, there isn't quite enough context in your reply for me to
understand exactly how you think this makes things worse for you.  Could
you expand, please?

> In that case I would prefer a statement discouraging systemd-specific
> features.

I doubt that we have project consensus on that.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature