| Summary: | bitbake-setup: build/conf change detection limited to source updates | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Clayton Casciato <ccasciato> |
| Component: | bitbake | Assignee: | Alexander Kanavin <alex.kanavin> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | poky.bs.watcher, poky.watcher, randy.macleod |
| Version: | 6.0 | ||
| Target Milestone: | 6.1 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Clayton Casciato
2026-03-25 03:23:02 UTC
But is this a real problem? Is there a use case? If you make modifications in build/conf, I don't think bitbake-setup should track what you do there and compare that against 'pristine' build/conf, if nothing has otherwise changed. That would be heavy handed: people modify build/conf all the time, and they don't need bitbake-setup telling them their local modifications caused the build to become 'out of date'. The build/conf comparison only kicks in when updates happened elsewhere (e.g. in config template, or layer revisions changed), because then build/conf may have changed as well, and it needs to be setup anew, and compared with the existing one. At that point there's no way to tell what was original, and what was added by the user. Bitbake-setup could potentially track that too (by putting a copy of the original build/conf into a local git under config/), but again, I do not see the use case clearly, but I do see increased code complexity that would result. Thanks for the feedback, Alex! I do not have a sample use case where this is required. Related to the original finding, it would be convenient to be able to configure the default value of `--update-bb-conf` (per Setup). This is most relevant for sans-fragment builds (e.g. Scarthgap), where the "no" option would be handy. Alex ? Alright. Closing for lack of clear use case. |