On Fri, 6 Jan 2023 at 19:52, Petr Kubizňák <[email protected]> wrote: > When the patch is _applied_ and g-i is _disabled_, graphene does build, but > some other packages don't:
... > This shows that these packages depend on gobject-introspection and/or its > dependencies no matter whether introspection is enabled or disabled. I don't > know these packages so I don't think I'm able to patch them properly. On the > other hand, I still believe it is incorrect to pull in the unnecessary > dependencies when g-i is disabled. What do you think? > This is what I was worried about. It uncovers a whole list of failures, and creates a new maintenance burden going forward, as fixing them will be an ongoing activity in the absence of an unconditional g-i dependecy.. If you have a bit of time, I'd suggest that you check the failures one by one. Some of it, like missing glib-* executables seems like a trivial missing dependency which was previously pulled in indirectly. Others, like python3-pygobject probably have a hard dependency on g-i. It does require navigating your way around unfamiliar source code, which is a useful skill in yocto regardless. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#175673): https://lists.openembedded.org/g/openembedded-core/message/175673 Mute This Topic: https://lists.openembedded.org/mt/96048399/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
