@@ -102,7 +102,7 @@ PACKAGECONFIG[polkit] = "-Dpolkit=true,-Dpolkit=false,polkit"
PACKAGECONFIG[bluez5] = "-Dbluez5_dun=true,-Dbluez5_dun=false,bluez5"
# consolekit is not picked by shlibs, so add it to RDEPENDS too
PACKAGECONFIG[consolekit] = "-Dsession_tracking_consolekit=true,-Dsession_tracking_consolekit=false,consolekit,consolekit"
-PACKAGECONFIG[modemmanager] = "-Dmodem_manager=true,-Dmodem_manager=false,modemmanager mobile-broadband-provider-info,modemmanager mobile-broadband-provider-info"
+PACKAGECONFIG[modemmanager] = "-Dmodem_manager=true,-Dmodem_manager=false,modemmanager mobile-broadband-provider-info"
PACKAGECONFIG[ppp] = "-Dppp=true -Dpppd=${sbindir}/pppd,-Dppp=false,ppp"
PACKAGECONFIG[dnsmasq] = "-Ddnsmasq=${bindir}/dnsmasq"
PACKAGECONFIG[nss] = "-Dcrypto=nss,,nss"
This reverts commit: 5edb8335dc46450fd6bcdbb3fcf55336b32bd422 The Networkmanager package must not depend on ModemManager. Only the Networkmanager-wwan package should depend on the ModemManager package. The mobile-broadband-provider-info is fully optional and it is often not required for embedded devices. Let the user choose if it gets installed or not. Adding it explicitely to IMAGE_INSTALL is simple. Adding an RRECOMMENS would work as well. But adding an RDEPENDS is bad. In general, NetworkManager packaging is intended to provide a set of binary packages suitable for building many different images. NetworkManager is designed to be used for binary packages distributions where it is not possible to rebuild NetworkManager just to install Modemmanager. Also for OE, where a rebuilding is possible, a rebuild is a disadvantage. So please do not destroy this flexibility by adding RDEPENDS, which are firstly wrong and secondly only suitable for your specific needs. Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> --- .../networkmanager/networkmanager_1.48.6.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)