| 1 |
On Fri, 21 Feb 2014 09:32:07 -0500, Tanstaafl wrote: |
| 2 |
|
| 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 |
> I'd also suggest throwing in a test for current running kernel config, |
| 14 |
> to make sure it fully supports booting with systemd, and maybe a new |
| 15 |
> emerge command that can also be maintained to make sure that *all* |
| 16 |
> necessary packages are rebuilt? |
| 17 |
|
| 18 |
That's already taken care of, the systemd ebuild checks your kernel |
| 19 |
config as part of the pre-emerge checks, nothing happens until you have a |
| 20 |
suitable kernel. |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Neil Bothwick |
| 25 |
|
| 26 |
If at first you don't succeed, redefine success. |
Archives