diff options
| author | Danilo M. <danix@danix.xyz> | 2026-06-24 17:07:16 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-06-24 17:07:16 +0200 |
| commit | d4ca425543752a370273a96af3f8606ab2b398cb (patch) | |
| tree | 27ddd46f075797382009a94aa5a17c4d6bc56ef3 /README.md | |
| parent | dcd063895865d9699ced0f063fe76be901a50184 (diff) | |
| download | sbo-batch-tester-d4ca425543752a370273a96af3f8606ab2b398cb.tar.gz sbo-batch-tester-d4ca425543752a370273a96af3f8606ab2b398cb.zip | |
Document package cache (CLAUDE.md, README)
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -73,6 +73,20 @@ The base is kept patched automatically on each run: when the mirror's ChangeLog head differs from the recorded marker, new packages from `patches/packages/` are applied to the local base via `upgradepkg`. +## Package cache + +Set `PKG_CACHE` in your config to a local directory to cache built packages +across runs (leave empty to disable). Layout mirrors the SBo tree +(`<category>/<prog>/<prog>-<version>-...txz`), one package per prog. + +The named target always builds fresh, it is the package under test. Its +dependencies are installed from the cache when their version is unchanged +(reported as `CACHED`), otherwise they are built and cached. A build order line +shows the outcome per package: `cached (1.1)`, `rebuild: 1.0 -> 1.1`, or +`build (new)`; `--dry-run` shows the same without building. The whole cache is +wiped automatically when the base is patched, since cached packages were built +against the previous base. + ## Usage ``` |
