On Tue, 1 Oct 2024 at 11:38, Richard Purdie <[email protected]> wrote: > > > The problem I'm trying to solve here is the reproducibility of > > > meta-openembedded. While oe-core world is always buildable, this > > > is, sadly, not the case for meta-openembedded layers. In order to > > > move forward with its reproducibility, we need to know the > > > reproducibility state of as much packages as possible. > > > > > > Do you think that goal is worth making the code more complex? Do > > > you have a suggestion on how to approach this? Making (and keeping) > > > meta-oe build every time is the goal, but history shows that it is > > > hard [0]. > > > [0]: https://autobuilder.yoctoproject.org/typhoon/#/builders/155 > > > > The real problem is that meta-oe isn't built in lockstep with oe-core > > changes, and regressions slip in all the time, and are fixed after > > the > > fact through heroic efforts of Khem and others. > > > > Maybe the new AB setup will allow including meta-oe builds into a- > > full? > > That pushes the problem to me and the core maintainers as we then have > to block until meta-oe is fixed as well with all the tracking and push > back on patches that involves. Is that really what we want to do?
I'm ok with handling a failing build, if v2 is possible and looks more maintainable than v1. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#205154): https://lists.openembedded.org/g/openembedded-core/message/205154 Mute This Topic: https://lists.openembedded.org/mt/108732482/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
