bundle.bbclass: do not generate SSTATE artifacts #324
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The artifacts created are quite large and keeping multiple of them will consume a notable amount of disk space while the expected speed-up is minimal. (For the same reasons, the image class does not generate SSTATE artifacts). Having SSTATE artifacts for bundles enabled can also lead to unexpected/unwanted behavior if a rootfs image recipe was rebuild and the binary output (file system image) changed but did not make it into the final bundle. This becomes a major problem, e.g. in the context of verified boot. Signed-off-by: Enrico Jörns <[email protected]>
Emantor
approved these changes
Jun 10, 2024
|
backported to |
|
backported to |
ejoerns
added
kirkstone
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The artifacts created are quite large and keeping multiple of them will consume a notable amount of disk space while the expected speed-up is minimal.
(For the same reasons, the image class does not generate SSTATE artifacts).
Having SSTATE artifacts for bundles enabled can also lead to unexpected/unwanted behavior if a rootfs image recipe was rebuild and the binary output (file system image) changed but did not make it into the final bundle.
This becomes a major problem, e.g. in the context of verified boot.