On Tue, Nov 03, 2020 at 01:37:01AM +0000, Jamie Heilman wrote: > socklog is now uninstallable on systems that don't use runit-init > which makes no sense. This program works without runit-init just > fine, there's no good reason for a hard dependency on runit-init.
Yes you are right, this was not intentional. The dependency is "runit-init | runit-run" to make it installable regardless of how runit is launched in the system, however I just notice that "runit-run", which replaced both "runit-sysv" and "runit-systemd", is only in experimental and not in unstabled. I totally overlooked that, sorry. I can change the dependency to "runit-init | runit-run | runit-sysv | runit-systemd" to support all methods of running runit on a system. Would that work for you, or would it already be too restrictive for your use case? The alternative would be to only depend on "runit", however the service would not necessarily start when the package is installed. People expect services to start on package installation on Debian. Cheers, -- Mathieu Mirmont <m...@parad0x.org>
signature.asc
Description: PGP signature
