Re: bitbake-setup in pip (was: [OE-core] Yocto Project Status 4 August 2026 (WW32))

Hi Alex,

Sounds good.  Sorry for not looping you in.

I have been working with Richard and Michael to transfer the PyPI repository to the Linux Foundation.  They already have been added as maintainers.

Richard and I discussed updating PyPI with a newer version in case people started using it.  I published 2.19 with the tip of the git tree: https://pypi.org/project/bitbake-setup/

Right now I am manually using twine to publish the package.  Some work needs to be done to add infrastructure to automate the testing and publishing of future releases.

I think it would be all set to go.  I encourage you to give it a shakedown and see if it fits your needs.

On a related note, I have been converting my kas configuration fragments into OE template fragments that both kas and bitbake-setup could use.  I would love to discuss some of these details with others interested in this area.

Regards,
Rob

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Alexander Kanavin <[email protected]>
Sent: Thursday, August 6, 2026 6:51:18 a.m.
To: Yocto-mailing-list <[email protected]>
Cc: ,[email protected] <[email protected]>; Woolley, Rob <[email protected]>; Richard Purdie <[email protected]>
Subject: bitbake-setup in pip (was: [OE-core] Yocto Project Status 4 August 2026 (WW32))

CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.

On Tue, 4 Aug 2026 at 17:07, Stephen Jolley via lists.openembedded.org
<[email protected]> wrote:
> Current Dev Position: YP 6.1 M3
>
> Next Deadline: YP 6.1 M3: w/c 2026-08-31

There was a question in the sync meeting about what people would like
to see in this cycle. I forgot to speak up: I'd like bitbake-setup
installable with pip :) I'm not 100% sure where we are with this right
now; I think all needed patches (or at least all published patches)
have merged, and what remains is the mechanics of making a release and
getting the artefacts to pypi.

The reason I'd like to see that is partly self-serving: I'm going to
talk about bitbake-setup (this time, as a released, shipped feature in
yocto) in ELC in Prague on 9 October, and it would be awesome to kick
it off with 'pip install bitbake-setup', rather than 'git clone
https://git.openembedded.org/bitbake'. But it's also good publicity
for the project to do it the former way.

So I'd like to hear from you Rob where we're at and if there's
something I could do, I'd be glad to.

Cheers,
Alex