Control: severity -1 normal
I don't get why this would be severity:critical.
With Recommends enabled, there are hundreds of packages that cause a
large-scale changeover of the system -- be it DE switch, installing a gig or
more of random daemons, an init system switch, or the like.
So unless the policy {lower-case} for Recommends gets changed (or rather,
its implementation all around Debian goes in line with the Policy wording),
there's no point in singling out this package.
> This is obviously not something a random user wants to do and have a
> large probability of destroying the system beyond repair.
Please file bugs for that "destroying the system beyond repair" if you can
name a case (preferably, not caused by broken Recommend chains elsewhere).
==========================================================================
But, let's discuss how to fix the issue at hand.
One idea:
Recommends:
runit-sysv | systemd-sysv | runit-init,
runit-systemd | sysvinit-core | runit-init,
runit-init | sysvinit-core | systemd-sysv
This is very unwieldy but wouldn't trigger an init switch in any case.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀ -- <willmore> on #linux-sunxi
⠈⠳⣄⠀⠀⠀⠀
