| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The PollScheduler class suffices here, if we just add a small amount of
logic to calculate the _background attribute from the emerge opts.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
EAPI 5 supports automatic rebuilds via the slot-operator and sub-slots,
which makes preserve-libs much more user-friendly, since it makes
@preserved-rebuild unnecessary (also see bug #364425 for explanation of
@preserved-rebuild shortcomings). Therefore, enable preserve-libs for
the stable branch, but not by default. After EAPI 5 is widely adopted,
we can consider enabling preserve-libs by default.
|
|
|
|
|
| |
This will allow for the option to be available in the stable branch
without changing the default --depclean behavior.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Since we're supposed to be able to efficiently obtain the EAPI from
_parse_eapi_ebuild_head, we don't need to write or trust cache entries
for unsupported EAPIs.
|
|
|
|
|
|
|
|
| |
This implements the specification that was approved in Gentoo's council
meeting on May 8, 2012 (see bug #402167). The parse-eapi-ebuild-head
FEATURES setting is now enabled by default, and causes non-conformant
ebuilds to be treated as invalid. This behavior will soon become
enabled unconditionally.
|
| |
|
| |
|
| |
|
|
|
|
| |
This will fix bug #409647.
|
| |
|
|
|
|
| |
This will fix bug #409085.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
A couple of recent commits touched this function, and code got moved
around unnecessarily.
|
|
|
|
|
| |
The first constructed config object initializes these modules, and
subsequent calls to the _init() functions have no effect.
|
| |
|
| |
|
|
|
|
|
| |
portage.dbapi.porttree.portdbapi objects. Migrate consumers to repositories
attribute of portage.dbapi.porttree.portdbapi objects.
|
|
|
|
|
| |
The portage_uid initialization here must to happend before the
_init_dirs() calls.
|
|
|
|
|
|
|
|
| |
This is handy for prefix installs, since it allows these variables to
be set in make.conf rather than having them hardcoded. Eventually,
the corresponding portage.data constants may be deprecated in favor of
config attributes, since it's conceivable that multiple configurations
with different constants could be used simultaneously.
|
|
|
|
| |
This fixes the case where $PORTDIR doesn't exist prior to sync.
|
|
|
|
|
|
| |
The fixes some cases where emerge.log would show that depclean was
unsuccessful when it was really successful but there was nothing to
remove.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
--info actions.
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
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).
|