1 |
Hi, |
2 |
|
3 |
Wol <antlists@××××××××××××.uk> writes: |
4 |
|
5 |
> On 15/02/2023 15:51, Daniel Frey wrote: |
6 |
>> On 2/15/23 06:10, Michael Orlitzky wrote: |
7 |
>>> On 2023-02-15 08:11:46, Neil Bothwick wrote: |
8 |
>>>> |
9 |
>>>> If, as you say, it will eventually replace eselect, there is no more |
10 |
>>>> bloat, just different bloat. It's still just a bunch of symlinks, but |
11 |
>>>> managed differently. |
12 |
>>>> |
13 |
>>> |
14 |
>>> Should be less, since you already have portage installed but not |
15 |
>>> necessarily eselect-whatever. |
16 |
>>> |
17 |
>> I didn't even know eselect-whatever was even an option until this |
18 |
>> post... It's not something I've ever used. |
19 |
>> It does (at least to me) make sense for the package manager to enforce these |
20 |
>> selections rather than some optional tool though. |
21 |
>> |
22 |
> what are they going to do about "eselect kernel set ..." then? |
23 |
> |
24 |
> It's bad enough depclean deleting the active kernel if you don't watch out, |
25 |
> without something deciding to install a non-existent kernel and deleting the |
26 |
> live one :-) |
27 |
|
28 |
This is part of the motivation behind the dist-kernel project. See: |
29 |
https://wiki.gentoo.org/wiki/Project:Distribution_Kernel |
30 |
|
31 |
As an anecdote, I haven't thought about what my kernel and modules are |
32 |
doing in a very long time, and I use multiple out of tree modules. |
33 |
|
34 |
Happy hacking and have a great day. |
35 |
-- |
36 |
Arsen Arsenović |