| 1 |
On Tue, 3 Jun 2014 07:35:42 -0400 |
| 2 |
Rich Freeman <rich0@g.o> wrote: |
| 3 |
|
| 4 |
> This probably could have used a news item, as the change impacts both |
| 5 |
> stable and ~arch users. |
| 6 |
|
| 7 |
Are we going to write a news item every time systemd acquires a new |
| 8 |
mandatory relationship with a reverse dependency? |
| 9 |
|
| 10 |
> They need to do an "emerge -1 sys-power/upower-pm-utils" to actually |
| 11 |
> get the new package, |
| 12 |
|
| 13 |
But the user doesn't want systemd; so, then why does the user have to |
| 14 |
perform a manual step every time that systemd has an acquirement? |
| 15 |
|
| 16 |
> otherwise portage is going to try to switch them from udev to |
| 17 |
> systemd, |
| 18 |
|
| 19 |
There is the problem, the user doesn't want systemd; so, why is Portage |
| 20 |
(regardless of a systemd mask) trying to bring it to the user anyway? |
| 21 |
|
| 22 |
> since packages like kdelibs list upower first, and portage |
| 23 |
> has no way of knowing that this is a big change. |
| 24 |
|
| 25 |
And this is where you can make Portage smarter. |
| 26 |
|
| 27 |
http://www.funtoo.org/Flavors_and_Mix-ins |
| 28 |
|
| 29 |
We don't have to go through all this if you had a "no-systemd" mix-in, |
| 30 |
where you could simply make out the choices in favor of the user |
| 31 |
instead of having to document and announce them all over the place. |
| 32 |
|
| 33 |
That mix-in could do something like masking the new upower that |
| 34 |
depends on systemd; when doing so, no more blockers all over the place. |
| 35 |
|
| 36 |
-- |
| 37 |
With kind regards, |
| 38 |
|
| 39 |
Tom Wijsman (TomWij) |
| 40 |
Gentoo Developer |
| 41 |
|
| 42 |
E-mail address : TomWij@g.o |
| 43 |
GPG Public Key : 6D34E57D |
| 44 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives