Hi, On Tue, Jun 28, 2011 at 09:07:12PM -0400, Olivier Crête wrote: > Hi, > > On Tue, 2011-06-28 at 17:10 -0500, William Hubbs wrote: > > The background is that /etc/init.d/functions.sh is a link to > > /lib/rc/functions.sh, which is part of openrc. > > > > Other init systems, like systemd, are coming along which completely > > replace sysvinit and do not use openrc's init scripts at all. However, > > since things other than init scripts are using /etc/init.d/functions.sh, > > all gentoo users are forced to have openrc on their systems whether they > > use its init scripts or not. > > > > As you can see in the bug, I am working on creating a > > minimalist version of openrc that can be installed to allow users to > > have access to the functions that are in functions.sh regardless of > > whether or not they are using openrc's init system. > > > > I'm not convinced that this is the best approach, so any input would be > > greatly appreciated. > > As long as we have Gentoo-style init scripts in the tree, we will need > these functions to be available. So yes, they should probably be in a > separate package from openrc itself to ease the transition to the bright > systemd future.
I'm not advocating killing openrc; I think that the sysvinit/openrc system we have is going to be our default init system for some time It isn't init scripts that I'm worried about. The problem is that scripts other than init scripts are using the code in /etc/init.d/functions.sh, so some how that code, or something similar to it needs to be available on systems so that someone, like yourself, who is not using openrc, can run "emerge --unmerge sysvinit openrc" and have a working system. Right now, things like revdep-rebuild and eix will break if you remove openrc. For the short term I can see it as a subset of openrc, but ultimately I think if you aren't using openrc's init system it should not be required on your system. Any other thoughts? William
pgp2KCLgV0LMi.pgp
Description: PGP signature
