Hi Richard,

No problem.  I had reservations about the version.py approach, so I'm glad
you provided that feedback.

I have some ideas, I'll take another run at it.

Regards,
Rob

On Fri, Mar 27, 2026 at 1:03 PM Richard Purdie via lists.openembedded.org
[off-list ref] wrote:

Hi Rob,

On Thu, 2026-03-26 at 10:39 -0700, Rob Woolley wrote:

quoted

We discussed how to version bitbake and bitbake-setup on a Weekly Tech
call at the end of January.

The initial proposal was to use the git tags in the bitbake git

repository

quoted

to dynamically determine the package version. There were complications in
this approach due to conflicting conventions between how the Yocto

Project

quoted

maintains git tags and the format accepted by PyPI.

A simpler alternative of using the version strings directly was proposed.
The request from Richard was to converge the 2 version strings for

bitbake

quoted

and bitbake-setup. He asked for it to be sent as a separate series from
the PyPI changes. He also asked for some sort of version checking in
case the scripts find the wrong version of the bb module.

Sorry, I think there has been a misunderstanding here :(. I asked that
we reconcile the version strings from bitbake and lib/bb/__init__.py

I'm worried that we might end up with a bin/bitbake being run but a
"lib/bb" coming from somewhere else. The current versions are compared
to check that but if we install bitbake-setup to somewhere, I'm not
sure how we'd continue to ensure this.

Putting a "version.py" into something we inject into PATH does worry me
a bit as it is a very generic name and it doesn't really avoid the
issue above I'm worried about.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19261):
https://lists.openembedded.org/g/bitbake-devel/message/19261
Mute This Topic: https://lists.openembedded.org/mt/118522774/556952
Group Owner: bitbake-devel+owner@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [
rob.woolleywr@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-