Currently, when NetworkManager is built without SystemD support, it automatically depends on ConsoleKit, which is also optional for NetworkManager. Somehow related upstream bugreport: session tracking: build in all modules (systemd, consolekit and none) and choose one at runtime https://bugzilla.gnome.org/show_bug.cgi?id=686997
Maintainers of net-misc/networkmanager have been CCed.
Not a major issue IMHO, we can wait for the next version bump before fixing it.
> Not a major issue IMHO, we can wait for the next version bump before fixing > it. Sure, no problem. I forgot to add that this issue was brought up by Michal Hrušecký (to give credit). We discussed it at LinuxAlt yesterday.
Just a little more feedback, as it doesn't change anything for people who already installed it, bump is not neccesary I beleive. And there is also optional policykit dependency. I was telling pavlix that I will not use anything that uses policykit and consolekit and he told me that my excuse doesn't aply to NetworkManager as both are optional :-D And now I have to give it chance...
Fixed in 0.9.6.4 and 0.9.6.4-r1. Sorry for the wait. +*networkmanager-0.9.6.4-r1 (25 Jan 2013) + + 25 Jan 2013; Alexandre Rostovtsev <tetromino@gentoo.org> + networkmanager-0.9.6.4.ebuild, +networkmanager-0.9.6.4-r1.ebuild, + metadata.xml: + Update to EAPI5 to clean up the ebuilds a bit. Allow disabling both + consolekit and systemd (bug #441756, thanks to Pavel Šimerda). Disable + systemd in 0.9.6.4 to allow stabilization; add 0.9.6.4-r1 with systemd + support.
