| Summary: | kde-plasma/powerdevil-5.24.4 wants to pull in networkmanager despite USE=-networkmanager set globally | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | kavol |
| Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
flags grouping features? You want the package to have two IUSE for a single functionality? I think everything was said already in the other thread. *** This bug has been marked as a duplicate of bug 644112 *** (In reply to Andreas Sturmlechner from comment #1) > flags grouping features? I think, if really needed, something like this would do: REQUIRED_USE=" bluetooth? ( networkmanager ) networkmanager? ( bluetooth )" > You want the package to have two IUSE for a single functionality? I don't know the internals ... is it really a single functionality? I mean ... if I have a device without bluetooth, do I really need to install bluez to be able to handle wifi? if I use connman, do I really have to install NetworkManager to enable some features handled by bluez? (In reply to kavol from comment #3) > I don't know the internals ... is it really a single functionality? Yes. Upstream did not provide separate handles for what they regard as one wireless devices power management feature. (In reply to Andreas Sturmlechner from comment #2) > I think everything was said already in the other thread. ok, this => "With powerdevil, upstream exposes a wireless feature that unconditionally requires both dependencies so that's what we expose." if only Bugzilla would not hide known (unfixed) bugs from the default search, it would save us this duplicate, and if only someone would rework this upstream ... :-/ |
Trying to install Plasma, I have found that something still wants to pull in NetworkManager despite I have the NetworkManager use flag disabled. Finally, I have found that this comes from powerdevil, the DEPEND section of the ebuild reads: wireless? ( >=kde-frameworks/bluez-qt-${KFMIN}:5 >=kde-frameworks/networkmanager-qt-${KFMIN}:5 ) and there is +wireless in IUSE Please split this and let it be controlled by the well established networkmanager and bluetooth use flags instead. If these really need to be pulled in together then use the flags grouping features which would be much more obvious than having to figure out by isolating dependencies and examining ebuilds why -networkmanager does not disable NetworkManager ... Reproducible: Always