While it is most certainly sensible and helpful on a system equipped
with Bluetooth and Wi-Fi hardware, it serves no purpose on a desktop
system without these and just pulls in a long chain of unwanted
dependencies.
Details
Details
- Reviewers
broulik - Group Reviewers
Plasma - Commits
- R122:3257be562b2c: Make NetworkManagerQt and BluezQt optional
Successfully built with BluezQt and NetworkManagerQt present and missing.
Diff Detail
Diff Detail
- Repository
- R122 Powerdevil
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
We've been through the "make action optional" dance with DPMS in the past and it has been a maintenance nightmare.
The action checks for whether you're allowed to enable/disable WiFi or else it won't show up. It seems it doesn't check for the existance of such hardware (except if the former implies the latter). This needs to be fixed, @jgrulich
Comment Actions
Sure, in the end you're the maintainer.
The action checks for whether you're allowed to enable/disable WiFi or else it won't show up. It seems it doesn't check for the existance of such hardware (except if the former implies the latter). This needs to be fixed, @jgrulich
That still would require said libraries and their dependencies, wouldn't it?
Comment Actions
That still would require said libraries and their dependencies, wouldn't it?
Yes. What dependencies are causing problems for you?
Comment Actions
Yes. What dependencies are causing problems for you?
NetworkManager and its dependencies mostly. If I compare the situation to kwin and kscreenlocker, for example, and its hard dependency on wayland there's an obvious benefit and wayland is rather small in size and dependencies.
Here I would install a bunch of software I would never use on my desktop and probably would even have to blacklist some parts of it in systemd, before it's started automagically and messes up my normal config (and yes, sadly that happened before).
Comment Actions
We already have a feature and dependency freeze in place. This should not have gone into the Plasma/5.7 branch!