| 1 |
On Tue, Jun 3, 2014 at 7:30 AM, J. Roeleveld <joost@××××××××.org> wrote: |
| 2 |
> On Tuesday, June 03, 2014 11:59:07 AM Alexander Kapshuk wrote: |
| 3 |
>> |
| 4 |
>> Just wanted to make sure I read the change logs shown below correctly. |
| 5 |
>> So far, I've been using sys-power/upower. Attempting to update |
| 6 |
>> sys-power/upower seems to require sys-apps/systemd to be pulled in as a |
| 7 |
>> dependency, which I don't want to do. |
| 8 |
>> |
| 9 |
>> If I understand the change log below correctly, I should uninstall |
| 10 |
>> sys-power/upower and install sys-power/upower-pm-utils instead. Is that |
| 11 |
>> right? Thanks. |
| 12 |
> |
| 13 |
> Sounds like Samuli is being a pr*ck by forcing systemd on everyone now. |
| 14 |
> A proper solution would have been to have the upower ebuild select systemd as |
| 15 |
> a dependency ONLY when the systemd useflag is set. |
| 16 |
> And depend on upower-pm-utils when it is not set. |
| 17 |
> |
| 18 |
|
| 19 |
Sounds like the original poster had the right answer. Starting a |
| 20 |
systemd flamewar is not helpful. |
| 21 |
|
| 22 |
"emerge -1 sys-power/upower-pm-utils" should fix this. |
| 23 |
|
| 24 |
However, this probably should have been a news item before going into |
| 25 |
the stable tree... |
| 26 |
|
| 27 |
Rich |
Archives