On Mon, Feb 24, 2014 at 02:16:20AM +0000, Duncan wrote: > What about putting the rebuild in a non-pkg_config function, then hooking > up that function to BOTH the above, so users can choose automatic rebuild > if they like, and regardless of whether they've done so, they can run > emerge --config runit any time to rebuild it independent of remerging the > entire package?
The problem is when to make it happen automatically. It will need to happen automatically when you upgrade to the new release I'm working on, 2.1.1-r2, only because I want to get the /etc/runit/runsvdir path out of the package contents. Once that happens, I can't think of a reason for the runit package to automatically touch that directory during upgrades. A first install might also be a case where it should be set up. Another possibility could be a change in the runit package itself that leads to a change in the default runlevels. Other than that, once this is set up, it doesn't need to be touched automatically. > Meanwhile, based on a decade plus of gentoo user experience, in practice, > emerge --config is obscure enough that using it in an ebuild tends to > hide it. If that's deliberate and the intent is a mostly one-shot > first-configuration run[1], emerge --config is a good choice. But if the > idea is to make configuration more routinely accessible not to hide it, > an alternative such as an eselect module or the various individual > package config tools (gcc-config for gcc, the rc-* tools for openrc, etc) > should be considered instead. 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. William
signature.asc
Description: Digital signature
