diff options
| author | Brian Harring <ferringb@chromium.org> | 2011-09-30 02:37:04 -0700 |
|---|---|---|
| committer | Zac Medico <zmedico@gentoo.org> | 2011-09-30 10:32:34 -0700 |
| commit | a72a01746638debe472496bd8fc661992a6ba08b (patch) | |
| tree | 68ab715443a3b4650a7440aad6179add386eba88 /pym/portage/cache | |
| parent | c2efbad8402a7e8904c7353a9930e87ea128b962 (diff) | |
| download | portage-a72a01746638debe472496bd8fc661992a6ba08b.tar.gz portage-a72a01746638debe472496bd8fc661992a6ba08b.tar.bz2 portage-a72a01746638debe472496bd8fc661992a6ba08b.zip | |
layout.conf: allow a repository to state the cache is authorative
By authorative, this means "the cache is accurate; skip validation". While
a useful hint for a slight speedup in validation, the true gain is for
repositories that are distributed in a fashion that doesn't preserve mtime;
git primarily. Setting authorative-cache = true results in portage
skipping mtime validation checks for the bundled cache, allowing
for git vcs based repos to distribute a cache.
BUG=chromium-os:21049
TEST=dump a cache into metadata/cache, touch it to now, set layout.conf
to authorative-cache=true, verify it doesn't generate cache entries
for that repo.
Change-Id: I92423e679bc171d2411a18d6d3ac22e8ef457753
Diffstat (limited to 'pym/portage/cache')
| -rw-r--r-- | pym/portage/cache/template.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/pym/portage/cache/template.py b/pym/portage/cache/template.py index f84d8f4b9..4cb27bff9 100644 --- a/pym/portage/cache/template.py +++ b/pym/portage/cache/template.py @@ -30,6 +30,7 @@ class database(object): self.readonly = readonly self.sync_rate = 0 self.updates = 0 + self.is_authorative = False def __getitem__(self, cpv): """set a cpv to values |