On Sat, Sep 7, 2024 at 11:22 AM Markus Volk <[email protected]> wrote: > > On Sat, Sep 7 2024 at 05:44:19 PM +02:00:00, Martin Jansa > <[email protected]> wrote: > > explicitly the external on (from oe-core) since > https://git.openembedded.org/openembedded-core/commit/meta/recipes-connectivity/ofono?id=3683f524dc60325b3f3b1bc3a32e70a41064ae03 > > > Understand. I also know that bluez5 uses ell when PACKAGECONFIG is enabled > for either mesh or btpclient. But that's not the default. So for consistency, > maybe it would be good to keep it external for all three? > > I'm not sure about this change either, but wanted to bring it up for > discussion because it always feels a bit like groundhog day with iwd/ell. > > I'm not that familiar with investigating sstate cache reuse issues. I'm > willing to learn more about it, but right now I don't know what exact files I > would need to compare, or is there something like a tool that can be used for > this purpose?
I think ell is in core layer therefore it binds us to the compatible versions we can use for packages which uses ell. It also depends upon how upstream is expecting distros to consume it. If they think that it should be vendored in apps then thats what we should do
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#112118): https://lists.openembedded.org/g/openembedded-devel/message/112118 Mute This Topic: https://lists.openembedded.org/mt/108319324/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
