Hi all, I'd like to revisit a topic I raised on the list some time ago: making `pip install bitbake-setup` a viable, stable alternative installation path for end users. As I recall, there was alignment from the BitBake community that having bitbake-setup properly published on PyPI was a desirable direction — it significantly alleviates the friction of getting started with BitBake/Yocto for developers who'd rather not clone a git tree as a build prerequisite (CI pipelines, container-based workflows, and newcomers in particular benefit).
To be clear on intent: we're not proposing pip as the primary install path. The git clone from git.openembedded.org/bitbake should remain the recommended approach, consistent with the Yocto Project Quick Build guide. The goal is simply to have pip work reliably as a documented alternative for those who prefer it. Looking at the current state, `pip install bitbake-setup` still resolves to 2.16.0a1 (an alpha from December 2025), which makes it hard to recommend even as an alternative. A few questions to move this forward: - 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. Thanks, -- 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 (#237312): https://lists.openembedded.org/g/openembedded-core/message/237312 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]] -=-=-=-=-=-=-=-=-=-=-=-
