Bug 16335 - Create more fine-grained buildtools
Summary: Create more fine-grained buildtools
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 6.2 M2
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2026-06-28 20:35 UTC by Yoann Congal
Modified: 2026-10-01 15:47 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yoann Congal 2026-06-28 20:35:37 UTC 
Current buildtools installs the whole set of tools[0]. When we need to add buildtools to a host to workaround a single host tool issue, we loose testing on every other tools.

Richard's idea[1] to avoid that: Create fine-grained buildtools: for exemple, one single buildtool dedicated to tar:
> I'm wondering if we should create a simpler "tar" buildtools tarball,
> to ensure other issues don't creep in on RHEL9 derivatives?
> [...]
> There is precedent for a single tool buildtools before when we had make
> issues with ./meta/recipes-core/meta/buildtools-make-tarball.bb
> (these days I'd class extend it!).

[0]: https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/meta/buildtools-tarball.bb
[1]: https://lore.kernel.org/yocto-patches/e9ee27ab791e38456ff57b535abe9d56eac60f76.camel@linuxfoundation.org/T/#mfe71608ae4817d6339e143bc715169b217d5e347