On 2014-02-21 4:58 PM, Neil Bothwick <n...@digimed.co.uk> 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.
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...
