On Mon, Feb 24, 2014 at 08:39:33AM +0000, Duncan wrote: > William Hubbs posted on Mon, 24 Feb 2014 02:14:54 -0600 as excerpted: > > Think of /etc/runit/runsvdir as being similar to /etc/runlevels in > > OpenRc. > > It is a directory that gets set up once, then only the admin should mess > > around in there by adding or removing directories (runlevels) and > > symbolic links to services. > > Hmm... Then pkg_config does seem an appropriate "hiding" and the parallel > to bind is even more striking. IIRC, when it massively reorganized the > chroot, it put an ewarn in pkg_postinst with some instructions, including > asking people to re-run emerge --config bind. IIRC it did NOT run that > reconfigure itself. > > Now making it a USE flag is a bit different, but the idea of making the > function independent and simply calling it from both pkg_config and > (conditionally on the use flag) pkg_postinst or whatever does seem > reasonable to me. I looked over how bind does this, and it doesn't use a use flag. it just provides instructions for the user to run emerge --config.
The /etc/runit/runsvdir directory is purely optional actually. It is upstream's recommended way to set up runit to support runlevels if runit is replacing sysvinit. However, a user can set up the service directory on their own. So I'm wondering if it is reasonable to just provide instructions to users to run emerge --config? William
signature.asc
Description: Digital signature
