Installing rcconf also installs sysv-rc, insserv, and startpar. Installing initscripts also installs sysv-rc, insserv, and startpar . If neither of those scenarios make sense without sysvinit installed, then yes, it clearly should be dependency somewhere. If insserv is not relevant on a systemd system, then please put in a conflicts.
As far as how it is even useful, honestly, I am not an expert on systemd (who is?). I had previously understood that rcconf on modern Debian systems interfaced with systemd through some sort of compatibility layer. The way that "sudo service lighttpd start" and "sudo systemctl start lighttpd" both do the same thing. This seems not to be the case. I don't know what all is involved under the hood for rcconf or Debian's init systems, nor should I have to. I should know what tools are available and expect that they will work. And if tool A is not compatible with initsystem B, then it's not unreasonable to expect that trying to install A when B is there will run into a conflict somewhere. So yes, if this is a nonsensical combination, please do put in the dependencies and conflicts that will enforce that for whatever packages you maintain. Thank-you. On 2021-05-05 00:20, Thorsten Glaser wrote: > On Tue, 4 May 2021, Kurt Fitzner wrote: > >> I just tried to install rcconf on a Debian testing sytem. Since rcconf > > How is rcconf even useful on a nōn-sysvinit+sysv-rc system? > > Maybe rcconf should depend on that or conflict with all others? > > bye, > //mirabilos
