| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This fixes a regression from the previous commit.
|
| |
|
|
|
|
|
|
|
| |
The PORTAGE_QUIET controls lots of stuff that really should only be
controlled by --quiet, especially now that --quiet-build is enabled by
default. For example, PORTAGE_QUIET supresses the successful checksum
display that is produced by emerge --fetchonly.
|
| |
|
|
|
|
|
|
| |
See discussion on the gentoo-dev mailing list:
http://archives.gentoo.org/gentoo-dev/msg_4f0401066abe2dc04458a952ac2a17bd.xml
|
|
|
|
|
| |
None of these cases should raise KeyError, but use get(REQUIRED_USE)
anyway to emphasize that care must be taken.
|
|
|
|
| |
This goes with commit a0961708ced50c90497811058eda6f4513d2986d.
|
| |
|
|
|
|
| |
--info actions.
|
| |
|
|
|
|
|
|
|
| |
It should be safe to assume that REQUIRED_USE is satisfied if the
package is built, so it's a waste to save it. Also, fix code which
assumes that built Package instances have a REQUIRED_USE key in their
metadata.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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)
|