hey there, so yeah zypper rm wpa_supplicant also wants to remove the whole NetworkManager stack
Seems like in that case, don’t remove it. It takes about 7 MB on disk, so shouildn’t be a big deal to leave it until the dependency is removed, if that’s planned.
Is there a way to declare the dependency as required only if iwd isn’t installed?
Something like:
Requires: wpa_supplicant >= 0.6.4 or iwd (i know that doesn’t work that way, I don’t know the real rpm spec code sorry)
instead of
Requires: wpa_supplicant >= 0.6.4
Why remove it??
(It’s a core component for securely connecting to wireless networks).
as said in the title, i switched the wifi backend to iwd
That would be a question for the packager to answer - they’ve determined the dependencies, and while you can force a removal that breaks dependencies, it’s not recommended.
There really isn’t a reason to remove it even if you switch the backend. I wouldn’t worry about it.
Yes, there is. Which is not the problem.
- just changing package does not mean that installation without
wpa_supplicant
is supported and works out-of-the-box. At the very least something needs to setiwd
as the WiFi backend inNetworkManager
. - there are several options that affect
NetworkManager
-iwd
interaction. It is completely unclear what values should be chosen as default on distribution level. - someone would need to handle bug reports resulting from using
iwd
as compared towpa_supplicant
.
If you volunteer to implement this and handle bug reports - by all means, prepare SR and convince maintainers to accept it.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.