On Tue, 2021-02-16 at 10:59 +0100, Konrad Weihmann wrote: > I'm a bit puzzled at the moment - after > fd6a007efa7cb45101a66f294af81d9d33bb3fab in meta-openembedded I faced a > lot of changes in the behavior of native-only recipes (@RP yes the ones > that don't use BBCLASSEXTEND :-)) > > after this change I had a couple of dependency loops like > > python3-my-recipe-native > python3 > ... > python3-my-recipe-native > > and I could track it down to distutils3-base.bbclass [1]. > There for all recipes no matter what the set (I guess BBCLASSEXTEND > magic will solves that in the end) "python3-native python3" is set in > DEPENDS. > > My question is, is that intended behavior or would it make sense to be > more explicit here, like > > DEPENDS += "python3-native" > DEPENDS_class-target += "python3" > > ? > > Mainly this happens when a globally inherited class requests a native > python3 package via DEPENDS (a not too uncommon use case for me). > > Thoughts?
Definitely a bug, I've sent a patch. The DEPENDS would be needed for nativesdk too and since it doesn't appear to require python3-native in the native case, I didn't change that. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#148168): https://lists.openembedded.org/g/openembedded-core/message/148168 Mute This Topic: https://lists.openembedded.org/mt/80674786/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
