On Tue, 2025-11-11 at 13:44 +0000, Alex Kiernan wrote: > On Tue, Nov 11, 2025 at 12:07 PM Richard Purdie via > lists.openembedded.org > <[email protected]> wrote: > > > > Having gone through trying to use bitbake-setup again, I'm sad to say > > that this isn't ready yet. > > > > The basic structure is there and is good but it has significant rough > > edges that cause usability problems and putting this in front of new or > > existing users is going to do the project reputation harm. > > > > I don't mind rough edges, but not when they're at the level they're > > currently at. > > > > I appreciate saying this instantly puts the pressure on me to say > > why/where it has issues and how to fix them. I will try and provide > > some thoughts on that but I am pretty burnt out at this point and not > > at my best. It is frustrating that I'm the one having to say this and > > that in saying it, I just make things worse for myself but it is what > > needs to be done. > > > > I had hoped more eyes, working through the docs and so on would let us > > get through this but as yet, that hasn't happened. I don't think we can > > release until we're in a better state. > > I started swapping over local builds to bitbake-setup this week, for a > basic qemu core-image-base it was impressively straightforward. > > But I've immediately run into things where I know how to do them in > the old world, but not the right way to do them in the new[1] and > failing to find answers in the docs, which isn't to say the answers > aren't there, I've just not found them. > > If there's things I could usefully help with documenting/testing, I've > got time on my hands as my current contract is on hold... > > [1] how do I add a layer which hasn't been migrated to bitbake-setup > was the first I hit
Firstly, lets drop the discussions after this reply to the bitbake- devel list, I don't think we need all three. The best place to start would be to write down the pain points you're finding. I think we all need to write down our findings, see if they are the same things or different ones. Once we have that data, a plan/direction might become clearer. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2201): https://lists.openembedded.org/g/openembedded-architecture/message/2201 Mute This Topic: https://lists.openembedded.org/mt/116237750/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
