| 1 |
On Wed, 4 Jun 2014 01:06:52 +0300 |
| 2 |
Alon Bar-Lev <alonbl@g.o> wrote: |
| 3 |
|
| 4 |
> Once again, you do not understand the claim. |
| 5 |
> |
| 6 |
> If a user of Gentoo chooses to use non systemd profile, it means that |
| 7 |
> we need to make sure systemd will not be a valid option, ever. |
| 8 |
|
| 9 |
There is no such thing as a "non systemd profile" on Gentoo at the |
| 10 |
moment; you have ".../systemd" profiles, which are specializations of |
| 11 |
the more generic case "..." which you can fill in with "gnome" or "kde". |
| 12 |
|
| 13 |
So, I'm here running this agnostic MATE with a make.profile symlink |
| 14 |
that doesn't point to a ".../systemd" profile; what is remarkable, is |
| 15 |
that systemd is a valid option in this case. |
| 16 |
|
| 17 |
Similarly, if I pick a ".../systemd" profile; what is remarkable, is |
| 18 |
that OpenRC is also a valid option in that case. |
| 19 |
|
| 20 |
For there to be a "make sure systemd will not be a valid option, ever" |
| 21 |
there would have to be a ".../no-systemd" profile or something like |
| 22 |
that; in such profile, one could then mask anything that tries to pull |
| 23 |
in systemd and not have to deal with further transitions later on. |
| 24 |
|
| 25 |
Splitting up profiles this way becomes a pain to maintain; other than |
| 26 |
that, it is also a controversial way to go about it given that a |
| 27 |
"no-..." type of profile hasn't been commonly used before yet. |
| 28 |
|
| 29 |
In this train of thoughts Funtoo mix-ins could help to do it more clean. |
| 30 |
|
| 31 |
http://www.funtoo.org/Flavors_and_Mix-ins |
| 32 |
|
| 33 |
But until we've got something, we've got to accept that other options |
| 34 |
remain valid choices; profiles are just there, well, to ensure a |
| 35 |
particular choice is properly supported without further implications. |
| 36 |
|
| 37 |
> In this case, if it is to disable the upower USE flag, or to provide |
| 38 |
> alternative, block newer version, whatever make it possible to have a |
| 39 |
> system working without systemd. |
| 40 |
> |
| 41 |
> systemd should not be visible at any time, nor its implications. |
| 42 |
> |
| 43 |
> Alon |
| 44 |
|
| 45 |
It is easy to make such a statement, but it is hard to make it happen; |
| 46 |
upstreams change over time, which makes such implications happen sooner |
| 47 |
or later in one place or the other. Which becomes visible over time... |
| 48 |
|
| 49 |
The manpower that we have to keep implications away are limited; to |
| 50 |
make a change to those implications, one could write code as suggested. |
| 51 |
|
| 52 |
-- |
| 53 |
With kind regards, |
| 54 |
|
| 55 |
Tom Wijsman (TomWij) |
| 56 |
Gentoo Developer |
| 57 |
|
| 58 |
E-mail address : TomWij@g.o |
| 59 |
GPG Public Key : 6D34E57D |
| 60 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives