New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/29115#issuecomment-787473473

Comment:
This is the wrong solution to a problem I'm not even sure exists. Almost everything in `runit-void` is tied to the assumption that runit is bringing up the system. The services in `/etc/sv` are only useful if `runsvdir` is used to manage system services, which is done by the scripts in `/etc/runit`. So keeping those separate from the init bits doesn't make sense. The same is true for the startup and teardown scripts in `/etc/runit`, which exist to be invoked by `runit` as PID 1.

About the only bits which might apply to alternatives to runit are `/etc/hostname`, `/etc/locale.conf`, `/etc/os-release`, `/usr/lib/dracut/dracut.conf.d/10-runit-void.conf` and, assuming alternatives like s6 are configured to invoke them, the trio of `/etc/rc.*` scripts. All you need to do here is move those files to another package. Maybe some of these belong in `base-files`; the Dracut configuration probably belongs in `dracut`.

Replacing runit with an alternative is a fine thing to do, but I don't think Void has the resources to provide any official support for swappable service management and init systems. Alternatives and virtual packages each cause problems that we probably don't want. To go down the path of runit altneratives, `ignorepkg` runit-void, install and configure what you want.