On Tue, 2022-01-11 at 12:02 +0100, Alexander Kanavin wrote: > On Tue, 11 Jan 2022 at 11:55, Richard Purdie > <[email protected]> wrote: > > > +# Kernel IP-Config is perfectly capable of setting up networking passed > > > in > > via ip= > > > +do_install:append:qemuall() { > > > + mkdir -p ${D}${sysconfdir}/default > > > + echo "export EXTRA_PARAM=\"-I eth0\"" > > > ${D}${sysconfdir}/default/connman > > > +} > > > > This means connman becomes machine specific, you can't do that. This would > > need > > to be done in the connman-conf recipe. > > I'm not sure I follow - the above instructs connman to ignore eth0 inside qemu > (and only inside qemu), why is that problematic?
The data above is inserted into /etc/default/connman in the connman package itself. That package is installed into deploy/XXX/<tunearch>/connman.YYY. That is not the machine specific package directory. Or in different words, if I build connmand for a qemu machine, then build connman for a machine with the same tune that isn't qemu, command rebuilds but installs the package to the same location. This is not allowed. Machine specific data (in this case qemu specific) shouldn't be in general packages. This goes against yocto-check-layer and YP-Compatibility. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#160393): https://lists.openembedded.org/g/openembedded-core/message/160393 Mute This Topic: https://lists.openembedded.org/mt/88311448/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
