All, there is a significant change I want to make to the sys-process/runit ebuild to fix a couple of bugs [1] [2].
In a nutshell, we set up a default runlevel as shown in this upstream document [3] in /etc/runit/runsvdir. We rebuild it every time an upgrade happens, so this is why we are hitting those bugs. I can think of two ways to handle building the runlevels which would leave them completely user maintainable after they are built. One is to use a use flag to build them. If I do that, I would consider forcing the use flag on with an iuse default, so anyone who doesn't want the runlevels rebuilt every time would need to turn it off in make.conf or package.use. The other way is to put this setup in pkg_config, which would mean a user would need to run "emerge runit --config" to have the runlevels built. The first way means that if you decide you want the runlevels built the way we build them you would need to emerge the package. The second way means that you could just use the --config option for emerge to rebuild them any time. Does anyone have any thoughts either way? Thanks, William [1] https://bugs.gentoo.org/show_bug.cgi?id=354053 [2] https://bugs.gentoo.org/show_bug.cgi?id=409469 [3] http://smarden.org/runit/runlevels.html
signature.asc
Description: Digital signature
