On Wed, 14 Jan 2026 at 19:38, Daiane Angolini via lists.openembedded.org <[email protected]> wrote: > We always knew bitbake-setup is in early stages, and there is a long > way until 6.0/may, that's why we started this conversation by asking > the basic questions: What is the expected list of features of > bitbake-setup by the next LTS and if bitbake-setup python package was > expected to be part of the LTS bundle before even start talking about > terminology. My goal (and I think I can say our goal and include > Otavio here) is more likely to be understanding where the community is > heading than making demands.
These questions are not particularly easy to respond to, and not all of what I want to say is 'pleasant'. I have a list of patches I'd like to get through the patch review: https://github.com/kanavin/bitbake/commits/akanavin/bitbake-setup/ There's another patchset from Corentin aiming to simplify sources format in the json. Adrian wants to integrate VSCode support. Rob wants to have a working pypi package, for which I wrote a patch to fall back to configuration registry if no internal registry is found (which is the issue you've reported). This patch is also in my patch queue. None of the above is a 'promise' or 'expectation' that it will happen in time for the LTS. Open source doesn't work that way. I'd love to implement all of the bitbake-setup wishes I got from you and others, but there's a number of high priority issues that need addressing, and they will take an unknown amount of time: https://bugzilla.yoctoproject.org/show_bug.cgi?id=16087 and a long list of other issues. You've been on the tuesday call, and you should know where help would be most appreciated. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#229393): https://lists.openembedded.org/g/openembedded-core/message/229393 Mute This Topic: https://lists.openembedded.org/mt/117262508/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
