Hi Richard, Thanks for the quick reply and the context — fully understood that the LTS feature freeze had to take priority, and we definitely don't want vendoring and versioning rushed just to hit a date. Getting those right matters more than getting it out fast.
Em ter., 19 de mai. de 2026 às 08:25, Richard Purdie via lists.openembedded.org <[email protected]> escreveu: > On Tue, 2026-05-19 at 08:20 -0300, Otavio Salvador wrote: > > - What's the current status of promoting bitbake-setup out of alpha > > on PyPI? Are there known blockers (release tooling, packaging, > > version coupling to BitBake/Yocto releases)? > > - Is the previously discussed plan still the intended direction, or > > has thinking shifted? > > - Would coordinating the PyPI release cadence with BitBake/Yocto > > releases be feasible, so users could pin to a known good version? > > > > Happy to help where I can if there are concrete blockers — packaging, > > release automation, documentation, or otherwise. > > We still have the intent of doing this and Rob Woolley posted some > initial patches on the bitbake mailing list. The timing was tricky with > the LTS feature freeze and we ended up focusing on getting the release > done. > > There are some logical steps such as needing to properly vendor the > bitbake modules and needing to work out a way to correctly version > bitbake's library and main scripts so that incompatible version > combinations error appropriately. > > The patches as posted currently aren't right, we're struggling with a > combination of review feedback and getting to the right patches... The reason I'm pushing a bit on timing: we're working on the fourth edition of our BitBake/Yocto book and are wrapping up the initial chapters to send to the technical reviewers. As mentioned before, we'd like to use bitbake-setup as the default installation path we recommend to readers. We're trying to cover the BitBake setup story as thoroughly as we can, and we genuinely believe pip is the more user-friendly option for newcomers — the git clone prerequisite is a real friction point before they've even built anything. Would it be fair to assume a non-alpha release on PyPI is realistic in the coming weeks? Even a rough sense would help us. If it's likely, we'll go ahead and structure the install chapter around `pip install bitbake-setup`. If the timeline is more open-ended, we'd rather know now so we can lead with the git clone path and keep the pip method as a forward-looking note. And the offer to help stands — happy to test Rob's patches, review packaging, contribute documentation, or whatever else would actually move things along. Thanks again, -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#237346): https://lists.openembedded.org/g/openembedded-core/message/237346 Mute This Topic: https://lists.openembedded.org/mt/119388663/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
