On Thu, May 30, 2013 at 02:06:42AM +0200, Tom Wijsman wrote:
> On Wed, 29 May 2013 15:55:23 -0500
> William Hubbs <williamh@gentoo.org> wrote:
> 
> > > We want to make this easier towards the user, therefore doing heavy
> > > discussion to exhaust all the alternatives and maybe someone's
> > > interested in implementing one of them that appears most feasible.
> > 
> > Since users can already do this, why are we bothering with
> > re-inventing the wheel? How does running an eselect init command make
> > it easier for the user than telling them to edit their boot loader
> > config file?
> >
> > Gentoo users are expected to build their kernel and write their boot
> > loader config file initially, so why are we trying to dumb this down?
> 
> For the same reason we have all the other eselect modules.
 
We could probably also turn gcc-config into an eselect module if we
want to use that argument.

> http://www.gentoo.org/proj/en/eselect/
> 
> Ironically, that project description even mentions init system... :)

Yes, but the init system module that project refers to is already there.
Check out eselect rc. It has nothing to do with switching init systems.
It appears to be a wrapper around rc-update and a couple of other things
to manage init scripts and runlevels.

Thanks,

William