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