[2019-08-30 23:38] Shengjing Zhu <z...@debian.org> > Package: runit-helper > Version: 2.8.13.2 > Severity: normal > > Please, don't do that. Don't let it be a second libsystemd0.
Well, I am not happy with this situation myself too, but I do not know do it better. `runit-helper` is essentially dynamically-linked maintainer script. I can easily put its content directly into maintainer script, and it will even solve some problems, but it will introduce new one: every change to what is now `runit-helper` would cause transistion. Was there, did that. I thought about dpkg triggers, but there is no reasonable way to convey required information to it. Also, triggers are meant to be idempotent, while `runit-helper' is not -- it must enable service on first installation, but must respect admin decision to disable it. Just for my curiosity (not going to happen in my watch), would you be happier if `runit-helper` script was part of init-system-helpers (which is essential, anyway). Another option I can propose is making call to `runit-helper` conditional, so you can dpkg-exclude whole `runit-helper` package. -- Note, that I send and fetch email in batch, once in a few days. Please, mention in body of your reply when you add or remove recepients.
