| 1 |
On 2014-02-21 4:58 PM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Fri, 21 Feb 2014 09:32:07 -0500, Tanstaafl wrote: |
| 3 |
>> Ok, so, since it really is so simple, wouldn't it be easier to |
| 4 |
>> implement this as an eselect module then, as opposed to creating a |
| 5 |
>> bunch of separate profiles? |
| 6 |
|
| 7 |
> profiles handle USE flags, eselect does not. Of course, you can use |
| 8 |
> eselect to change profiles :) |
| 9 |
> |
| 10 |
> It's not as complex as creating a lot of different systemd profiles |
| 11 |
> because of inheritance. |
| 12 |
|
| 13 |
Thanks Neil, but... what are you suggesting then? That it would have to |
| 14 |
be done as profiles, but it wouldn't be really complicated? Or maybe |
| 15 |
that it would be a combination of profile selection and... something |
| 16 |
else (new eselect init module)? |
| 17 |
|
| 18 |
Remember, I want all of this to coalesce into an enhancement/feature |
| 19 |
request for gentoo to be able to provide a sound, sane way to manage the |
| 20 |
idea of switching init systems. |
| 21 |
|
| 22 |
>> I'd also suggest throwing in a test for current running kernel config, |
| 23 |
>> to make sure it fully supports booting with systemd, and maybe a new |
| 24 |
>> emerge command that can also be maintained to make sure that *all* |
| 25 |
>> necessary packages are rebuilt? |
| 26 |
|
| 27 |
> That's already taken care of, the systemd ebuild checks your kernel |
| 28 |
> config as part of the pre-emerge checks, nothing happens until you have a |
| 29 |
> suitable kernel. |
| 30 |
|
| 31 |
Ok, excellent... |
Archives