aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorRobin H. Johnson <robbat2@gentoo.org>2017-12-06 00:45:30 -0800
committerRobin H. Johnson <robbat2@gentoo.org>2017-12-06 10:05:00 -0800
commitd0fc244d633375faeaf4da81350c9818a1b291f0 (patch)
tree68100d3703cd6f2edd7cba55df34b64ed33c6340 /doc
parentkmerge.sh: ensure bc is installed when kerncache is active (diff)
downloadcatalyst-d0fc244d633375faeaf4da81350c9818a1b291f0.tar.gz
catalyst-d0fc244d633375faeaf4da81350c9818a1b291f0.tar.bz2
catalyst-d0fc244d633375faeaf4da81350c9818a1b291f0.zip
Allow unversioned cache directories
The generation of cachedirs up to this point includes the version_stamp from the specfile. If the version is being automatically incremented (eg daily builds), then it generates unique cache directories for each build, and doesn't reuse old cache. Example versioned cache directories: /release/buildroot/amd64-dev/packages/default/stage1-amd64-20171203 /release/buildroot/amd64-dev/packages/default/stage1-amd64-20171204 /release/buildroot/amd64-dev/packages/default/stage1-amd64-20171206 This should be using a common cache directory: /release/buildroot/amd64-dev/packages/default/stage1-amd64 Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> Signed-off-by: Brian Dolbec <dolsen@gentoo.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/catalyst-config.5.txt9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/catalyst-config.5.txt b/doc/catalyst-config.5.txt
index 5c5ad293..957ab0e6 100644
--- a/doc/catalyst-config.5.txt
+++ b/doc/catalyst-config.5.txt
@@ -145,6 +145,10 @@ Cache the snapshot so that it can be bind-mounted into the chroot.
WARNING: moving parts of the portage tree from within fsscript *will*
break your cache. The cache is unlinked before any empty or rm
processing.
+
+versioned_cache::
+Name the cache directories (packagecache, kerncache) based on the version of a
+spec file.
--
Repository settings
@@ -240,9 +244,14 @@ sub-slots, you may experience errors like this due to untracked ABI
missmatches in binary packages. Packages generated by catalyst builds
are currently namespaced:
+If versioned_cache is set:
---------------------------------
.../packages/<rel_type>/<target>-<subarch>-<version_stamp>/Packages
---------------------------------
+Otherwise:
+---------------------------------
+.../packages/<rel_type>/<target>-<subarch>/Packages
+---------------------------------
so running into these out-of-date packages is unlikely. You may run
into problems if: