William Hubbs posted on Mon, 24 Feb 2014 02:14:54 -0600 as excerpted: >> 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.
> 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. And (as you may well be aware) I'd very likely disable that USE flag here (well, USE=-* and not enable it elsewhere), because my init setups tend to make rather complex use of advanced out of the ordinary corner-case features, thus the reason I ultimately ended up on openrc-9999 and generally git-logging every single change before I even install the update, let alone reboot. But hey, I've found and reported a number of openrc bugs so they could be fixed before they ever appeared in a release over the years as a result, too. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
