On Wed, May 29, 2024 at 04:37:30PM +0200, Lorenzo wrote: > just to make sure that the info is complete:
Both of your points are FUD. > the patch adds a dependency in the form > > systemd | systemd-standalone-sysusers | systemd-sysusers > > with the above by default, on an alternative init system, apt > wants to remove your init system and intall systemd. A quick check on a current Debian unstable with runit-init, and with or without elogind, shows that there is no problem. stunnel4 is a package using the dependency as you show: | # dpkg -l runit-init | egrep '^ii' | ii runit-init 2.1.2-54 arm64 system-wide service supervision (as init system) | # apt install stunnel4 | Reading package lists... Done | Building dependency tree... Done | Reading state information... Done | The following additional packages will be installed: | systemd-standalone-sysusers | Suggested packages: | logcheck-database | The following NEW packages will be installed: | stunnel4 systemd-standalone-sysusers | 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. > Another issue is that it contributes to make it impossible to switch > a system from systemd to another init system; I recently tried in > virtualbox and could not do it even using dpkg --force-depends, thanks > to elogind plus other important packages like udev and > cron-dameon-common that are using this kind of dependency. See above. It just works. There is no need for --force-depends or any trickery, except what you documented yourself: init has to be removed to install runit-init. Chris
