On 04/06/2014 00:06, Alon Bar-Lev wrote: > On Wed, Jun 4, 2014 at 12:59 AM, Canek Peláez Valdés <can...@gmail.com> wrote: >> >> On Tue, Jun 3, 2014 at 4:40 PM, Alan McKinnon <alan.mckin...@gmail.com> >> wrote: >> [...] >>> Incidentally, what exactly is wrong with systemd writing a dhcp server & >>> client, and an ntp client? Is that project prohibited from writing such >>> software? Are they not allowed to do it? Does it break legal laws? Is >>> there an NDA or non-compete clause in the mix that I'm not aware of? >>> Because they are the only things that could stop systemd from writing >>> such code; without such prohibitions they are free to spend their time >>> doing whatever they damn well please and if that means yet another dhcp >>> implementation, so be it. >> >> Alan, thanks for succinctly putting why is absurd to complain about >> someone else's desire to write whatever code she desires to write. And >> to sharing it to the world! The HORROR! >> >> How *DARE* they to release their code? For free! >> > > Once again, you do not understand the claim. > > If a user of Gentoo chooses to use non systemd profile, it means that > we need to make sure systemd will not be a valid option, ever. > > In this case, if it is to disable the upower USE flag, or to provide > alternative, block newer version, whatever make it possible to have a > system working without systemd. > > systemd should not be visible at any time, nor its implications. > > Alon
Alon, You need to read the massive thread on -dev about this and understand the technical reason why portage is doing something strange. I'm not going to give you opinion or rant here, I'm going to give you fact: Nobody is shoving systemd down anyone's throat because that is not what the portage code did. UPower removed their support for pm-utils (unmaintained for 5 years) and now support that same functionality provided by systems. UPower has the right to make that call. Samuli picked up that this is an issue for non-systemd users - they will not have the ability to suspend/hiberate. So a package was created called upower-pm-utils which contains the pm-utils code prior to the UPower change. If you want UPower to work as it always did for you, simply unmerge upower and merge upower-pm-utils. To have suspend/hibernate done the systmed way, just leave UPower installed and let portage do it's thing. Now, this is where the snag comes in. Portage sees you have UPower and you now need pm functionality, and portage needs to merge something to fill that dependency. Because of the way the code works, portage finds UPower+systemd first always, and decides to use that. It's software, not a human, so it doesn't question your decision and proceeds. It's analogous to having a virtual - if you don't tell portage which one to use, it picks the first. You tell portage which one you want by installing it, and portage is happy with that. Should there have been some USE flag-type solution to definitely indicate your choice? Sounds good in practice but in this case it's not a good idea (see the -dev thread for reasons why). Besides, this is a transitional phase and things will change again in a month. It's really not worth the effort to set up a USE for one package for a month. Those are the facts as laid out by our Gentoo devs and those facts do not support a conspiracy theory. Summary; You yourself do not want systemd. OK. Here's how to not get it in this case: emerge -C upower && emerge -1 upower-pm-utils -- Alan McKinnon alan.mckin...@gmail.com
