Cache clean-up fix.

[PawelWMS]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Update to #10369.

The original change made the toolkit always clean-up the downloaded RPMs cache, even if the repo snapshot flag was not set. This broke scenarios, where a use pre-populates the cache with hydrate-cached-rpms. Now the cache will only be cleaned-up if the PACKAGE_CACHE_SUMMARY or REPO_SNAPSHOT_TIME flag is set. Running with PACKAGE_CACHE_SUMMARY is another scenario, where we need to purge the cache before we run the package fetcher.

Does this affect the toolchain?

No.

Associated issues

• Add REPO_SNAPSHOT_TIME to the toolkit for package and image build. #10369

Test Methodology

• Fast-track 3.0 build.