kde-plasma/plasma-workspace-5.2.95 brings unwanted kde-frameworks/networkmanager-qt and net-misc/networkmanager. I am using systemd-networkd for network configuration, and networkmanager is not needed for my system. Maybe this deps can be moved to USE flag? Reproducible: Always
AFAICS that's needed for geolocation. I did not look at the code, but most likely it should be easier to make geolocation (and with it networkmanager) optional instead of trying to make networkmanager optional within geolocation...
Correct, it's hard-required by upstream as part of geolocation. I'm fine with hiding geolocation behind a USE flag, but I don't know what might break with it missing.
And it (once again) broke my network setup. Really great if such automated solutions overwrite global (working) config files, in my case /etc/resolv.conf. I just don't want to dive into yet another system to figure out how to disable it... Sry about the rant... If I had time now I would try to patch it out myself.
(In reply to Michael Palimaka (kensington) from comment #2) > Correct, it's hard-required by upstream as part of geolocation. I'm fine > with hiding geolocation behind a USE flag, but I don't know what might break > with it missing. Please do it, or at least try: I don't want (or need) networkmanager on my system.
There's an upstream thread about this issue currently: https://mail.kde.org/pipermail/plasma-devel/2015-May/041825.html Unfortunately, an upstream solution is, as expected, unlikely.
(In reply to Michael Palimaka (kensington) from comment #5) > There's an upstream thread about this issue currently: > https://mail.kde.org/pipermail/plasma-devel/2015-May/041825.html > > Unfortunately, an upstream solution is, as expected, unlikely. My guess is that networkmanager will be replaced with networkctl (systemd) in the long term and then the dependency will be removed of course.
*** Bug 559150 has been marked as a duplicate of this bug. ***
As no progress upstream, I opened a bug at kde[1] to track this, I am very side that approach of KDE has changed. [1] https://bugs.kde.org/show_bug.cgi?id=352275
I'm happy to carry a downstream patch, but we need to be sure that any such patch will not cause other bugs or issues. Disabling the geolocation dataengine certainly would be the simplest option - but there's no way of knowing what other effect that might have.
(In reply to Michael Palimaka (kensington) from comment #9) > I'm happy to carry a downstream patch, but we need to be sure that any such > patch will not cause other bugs or issues. Disabling the geolocation > dataengine certainly would be the simplest option - but there's no way of > knowing what other effect that might have. On Exherbo we also had a discussion: https://galileo.mailstation.de/gerrit/#/c/1808/ Resulting in the following commit: https://git.exherbo.org/kde.git/commit/packages/kde?id=abc38e668eab1828415c8e6506ebe04d663f4360 Maybe it's of any help/use.
I checked on lxr and couldn't find anything released that uses the geolocation dataengine so pushed this for testing: https://gitweb.gentoo.org/proj/kde.git/commit/?id=91002a490d380f2b09b4b9c6dff8bcaf33d89633
(In reply to Michael Palimaka (kensington) from comment #11) plasma-workspace-9999[-geolocation] builds here fine now without installed networkmanager / networkmanager-qt Thanks
(In reply to Michael Palimaka (kensington) from comment #11) > I checked on lxr and couldn't find anything released that uses the > geolocation dataengine so pushed this for testing: > https://gitweb.gentoo.org/proj/kde.git/commit/ > ?id=91002a490d380f2b09b4b9c6dff8bcaf33d89633 I backported the patches to plasma-workspace-5.4.1 ebuild and it builds and works fine.
Thanks, this is in the main tree as part of 5.4.2
kde#352275[1] resolved, should not be an issue any more. [1] https://bugs.kde.org/show_bug.cgi?id=352275
