If the "rm_work" task runs on these recipes, the next execution of the do_sbom_cve_check task would force the CVE databases to be extracted again. Excluding the recipes from "rm_work" allows the build system to remember that the unpack and patch tasks were already executed, so it does not run them a second time. Extracting the CVE databases is slow, and it also removes the database "index", which sbom-cve-check has to regenerate — an even slower step.
Keeping WORKDIR around is cheap: for the recipes downloading the CVE databases, it stays below 400 kB (not counting the "temp" directory, which rm_work leaves in place anyway). Signed-off-by: Benjamin Robin (Schneider Electric) <[email protected]> --- meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc index fbdc561e8c6a..2efc080b9327 100644 --- a/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc +++ b/meta/recipes-devtools/sbom-cve-check/sbom-cve-check-update-db.inc @@ -2,6 +2,7 @@ INHIBIT_DEFAULT_DEPS = "1" EXCLUDE_FROM_WORLD = "1" +RM_WORK_EXCLUDE += "${PN}" inherit native require conf/sbom-cve-check-config.inc --- base-commit: 934e84e9ea1fa2faf14bdafa71638fdca22dd79a change-id: 20260904-sbom-cve-check-update-db-no-rm-work-0bdb71d35fbc Best regards, -- Benjamin Robin (Schneider Electric) <[email protected]>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#245072): https://lists.openembedded.org/g/openembedded-core/message/245072 Mute This Topic: https://lists.openembedded.org/mt/121083096/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
