Re: [bitbake-devel] [PATCH 5/6] lib: Vendorize bundled third-party libraries under bb._vendor

On 31 Mar 2026, at 15:53, Rob Woolley via lists.openembedded.org <[email protected]> wrote:
> 
> Move ply, progressbar, simplediff, and bs4 from lib/ into
> lib/bb/_vendor/ to avoid conflicts with system-installed versions
> and to support proper packaging. These libraries contain local
> modifications from their upstream versions.

I’d like to see the vendoring done with a tool that lets us update the bundled libraries easily in the future, to be honest.

When I wrote picobuild (now redundant as pypa/build can bootstrap itself) I used the same tool that pip uses to vendor its dependencies: https://github.com/pradyunsg/vendoring.  So https://gitlab.com/rossburton/picobuild is a minimal example of using vendoring: a few lines of configuration in pyproject.toml and a separate requirements file.

Obviously if we sync from upstream we’ll drop our local changes, so the question then is why do we have forks?  Note that vendoring can apply patches when it updates, so if there’s a simple but not-upstreamable change we can carry the patch in-tree.

Ross