On 22/02/2014 18:37, Tanstaafl wrote: > On 2014-02-21 4:58 PM, Neil Bothwick <[email protected]> wrote: >> On Fri, 21 Feb 2014 09:32:07 -0500, Tanstaafl wrote: >>> Ok, so, since it really is so simple, wouldn't it be easier to >>> implement this as an eselect module then, as opposed to creating a >>> bunch of separate profiles? > >> profiles handle USE flags, eselect does not. Of course, you can use >> eselect to change profiles :) >> >> It's not as complex as creating a lot of different systemd profiles >> because of inheritance. > > Thanks Neil, but... what are you suggesting then? That it would have to > be done as profiles, but it wouldn't be really complicated? Or maybe > that it would be a combination of profile selection and... something > else (new eselect init module)? > > Remember, I want all of this to coalesce into an enhancement/feature > request for gentoo to be able to provide a sound, sane way to manage the > idea of switching init systems.
eselect is not going to work and neither is a Gentoo profile. eselect manages config options between different implementation of a thing. Usually by tweaking symlinks. Switching init OpenRC <-> SystemD involves resetting uSE flags and recompiling some fundamental stuff. That exercise is unlikely to ever go into eselect. The devs on gentoo-dev already nuked the idea of a gentoo profile as such, it's not worth the effort and causes an explosion of profiles. Switching to and from systemd is a few simple steps: - Change some USE - Recompile some stuffs - maybe read a howto or two - in all likelihood reboot Conceptually, it is rather similar to switching between nouveau and nvidia. That doesn't have eselect support[1] or profiles. To switcvh to and from >>> I'd also suggest throwing in a test for current running kernel config, >>> to make sure it fully supports booting with systemd, and maybe a new >>> emerge command that can also be maintained to make sure that *all* >>> necessary packages are rebuilt? > >> That's already taken care of, the systemd ebuild checks your kernel >> config as part of the pre-emerge checks, nothing happens until you have a >> suitable kernel. > > Ok, excellent... > > > -- Alan McKinnon [email protected]
