| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
This controls whether or not the layout.conf
"authoritative-cache = true" setting will be trusted for a particular
repo. It can be enabled globally by setting
"trust-authoritative-cache = true" in the [DEFAULT] section of
repos.conf.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
This fixes a false --binpkg-respect-use warning that's triggered by
erroneous USE/IUSE comparison between the new-style virtual and an
old-style virtual match.
|
|
|
|
|
|
|
| |
This causes new-style virtuals to get pulled in for virtuals that are
already satisfied by installed old-style virtuals. This case is common,
due to PROVIDE being (removed without revision bump) from lots of
ebuilds.
|
|
|
|
|
|
|
|
| |
This removes a special case where manifests would first be commited
without signatures for category-level or greater commits. This case
behavior wasn't very useful anyway, and would be a problem if the
unsigned manifests got rejected by a commit hook (as may happen in the
near future).
|
| |
|
|
|
|
|
|
| |
Since the change involving slot conflict parent atoms in commit
6cea2091526659521d35be6c8dc7733f69f1a760, we want to check to make
sure we don't display any false positives in the "missed updates".
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This narrows the range of possible behaviors, such that the manifest
will always be either written or unlinked, eliminating the possiblity
that a stale manifest will ever be allowed to slip through without
being overwritten or unlinked.
|
|
|
|
|
|
|
|
|
|
|
| |
This adds three states to layout.conf key use-manifest; false, true, and strict.
false means "don't use manifests at all"
true means "use and generate manifests, but allow them to be missing"
strict means "manifests must be used everywhere in this repo"
BUG=chromium-os:11308
TEST=repoman manifest usage.
|
| |
|
| |
|
| |
|
|
|
|
| |
Change-Id: I92890279dc69974da94cc9a8a5483ddd295512d4
|
| |
|
|
|
|
|
| |
We want to return an empty list for the match-* methods, otherwise an
empty string.
|
| |
|
|
|
|
| |
This eliminates redundant code.
|
|
|
|
| |
This eliminates redundant code.
|
|
|
|
|
| |
This allows match-visible to avoid calling match-all, which allows it
to avoid an extra loop over all repos.
|
|
|
|
|
|
| |
Also, make repoman cache IUSE, since that's required for _match_use to
work effciently. This will eliminate lots of redundant aux_get calls
for repoman, triggered by USE deps.
|
| |
|
|
|
|
|
| |
This optimizes aux_get and cp_list for cases where we only have a
single tree, which is common for repoman and ebuild(1).
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This allows use to avoid using a set to eliminate duplicates, since we
can break out of the repo loop as soon as a given cpv is found to be
visible.
|
| |
|
|
|
|
|
| |
There's no need to have separate methods, and this allows us to avoid
using separate aux_get calls in each method.
|
| |
|
|
|
|
| |
These don't mesh well with multi-repo support.
|
| |
|
|
|
|
|
| |
This is a regression from commit
3d07f74a2fb2e0480e126335f6981218f60da824.
|
|
|
|
|
| |
in addition, omit the leading slash, since PORTAGE_CONFIGROOT contains a
trailing slash
|
| |
|
| |
|
|
|
|
|
| |
This reverts commit dd7c57ecb90949ce3306394cfe262566b87351ca.
We'll do this in a new EAPI, as discussed in bug #384147.
|
|
|
|
| |
This will fix bug #384147.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This will fix bug #384063. The xmatch list-visible mode was previously
used to cache a list of all visible cpvs for a given cp, but this is
not useful when there can be duplicate cpvs with different visibility
from multiple repos.
|
| |
|