| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This eliminates a bunch of redundant eclasses code that we handle with
template.validate_entry() instead.
|
| |
|
| |
|
|
|
|
|
| |
This borrows the approach that egencache uses since commit
0e120da008c9d0d41c9372c81145c6e153028a6d.
|
|
|
|
|
|
| |
This adds support to action_metadata() for use of arbitrary validation
methods, which were introduced in commit
2ed1cb53cc4158af08c22d466b15b9a9a7767212.
|
|
|
|
|
| |
This has been broken since metadbmodule support was removed in commit
d4ea29bf6a3ce35d49e0f54f9173e3a6e42da2d6.
|
| |
|
| |
|
|
|
|
|
|
| |
This simplifies the checks since the bytes type is available in all
supported python versions, while the unicode type is only available in
python2.
|
|
|
|
| |
There's an extra level for the @property wrapper.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
count_unread_news(portdb, vardb, repos=None, update=True)
display_news_notifications(news_counts)
|
|
|
|
|
|
|
|
|
|
| |
It makes more sense to use EROOT instead of ROOT for keys in mappings
like portage.db, since it allows for multiple prefixes to exist
simultaneously within the same map without having a key collision.
This affects all portageq commands which take a <root> parameter, since
that parameter now corresponds to EROOT instead of ROOT. None of this
makes any difference for non-prefix users, since EROOT and ROOT are
identical when EPREFIX is empty.
|
| |
|
| |
|
|
|
|
|
|
| |
In preparation for prefix support, were EROOT will be used in place of
ROOT in many places, deprecate unnecessary "root" attributes in order
to eliminate them as a possible source of confusion.
|
| |
|
|
|
|
|
| |
This warning has been broken since commit
5f65c2294df592a6a4e0f0fff0bedec49ed3491a.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This options disables creation of binary packages, no matter
what enabled it in the first place. See bug 386903.
|
| |
|
|
|
|
|
| |
For parse-eapi-ebuild-head, we want to assign self.metadata from the
return value, for conformity with usage elsewhere.
|
|
|
|
|
| |
This fixes bugs that can only be triggered by egencache since
other callers handle parse-eapi-ebuild-head earlier.
|
|
|
|
|
| |
This fixes a regression in FEATURES=parse-eapi-ebuild-head support
for egencache since commit 2ed1cb53cc4158af08c22d466b15b9a9a7767212.
|
| |
|
|
|
|
|
|
|
|
| |
Since changes to eclass validation code in commit
2ed1cb53cc4158af08c22d466b15b9a9a7767212, validation of cache for
packages with empty INHERITED metadata has been broken due to failure
to distinguish between None and empty dict return values from
eclass.cache.validate_and_rewrite_cache().
|
|
|
|
|
|
| |
The hunk that got removed from action_metadata in commit
d4ea29bf6a3ce35d49e0f54f9173e3a6e42da2d6 is actually needed when
FEATURES=metadata-transfer is enabled.
|
|
|
|
|
|
|
|
|
|
| |
Specifically, the cache can use any portage supported checksum method,
or use the standard mtime approach. In addition, support controlling
whether or not paths are stored, and generally try to restore some
of the centralization/encapsulation that was in place originally.
(cherry picked from commit bc1aed614fb588f0ade5bcb5d1265a8db0f8d247)
Change-Id: Ic38057e7dbb15063c64a93c99e66e113a7d4c70e
|
|
|
|
|
|
|
| |
Looks of it, this code was copied/mangled into action_metadata; the
noise/callbacks in use don't do anything, so drop them, the dead code,
and clean up the exception handling to reflect the new reality
(cherry picked from commit 320890fadbedf678119ac06d458ed6086075431e)
|
|
|
|
|
|
|
|
|
|
|
| |
Controllable via 'cache-format', currently it supports only one cache;
'pms', and defaults to it. If an unsupported cache-format is specified,
the cache is disabled. If pms is specified and metadata/cache directory
doesn't exist, the cache is disabled.
Finally, this rips out the best module support for locally overriding
the cache format used for pregenerated caches; this functionality made
zero sense (upstream determines the format, we use what is available).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it possible to disable the dynamic dependency updates that
FakeVartree performs by default.
WARNING: If --dynamic-deps is disabled, then it is necessary to
ensure that an alternative method is used to handle package moves
in dependencies of installed packages. Normally, this is handled
by FEATURES="fixpackages", which is enabled by default and may be
disabled via make.conf(5). Alternatively, in order to manually apply
package moves, run `emaint --fix moveinst` after each emerge --sync
operation (see emaint(1)).
|
|
|
|
| |
Bug #286201
|
| |
|
|
|
|
|
|
|
|
| |
The slot conflict display has better noise reduction than the
unsatisfied blockers display, so skip unsatisfied blockers display if
there are slot conflicts (see bug #385391). Note that this reverses
the logic from bug 159310, since the slot conflict display has evolved
a lot since then.
|
|
|
|
| |
This will fix bug #385413.
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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 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.
|