| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This removes the last reference to PORTAGE_CALLER.
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
There's no need to query os.environ here, because portage.settings
will inherit the value automatically.
|
| |
|
|
|
|
|
|
|
|
| |
This code should be unnecessary, as long as the repo is correctly
identified for all calls to portdbapi methods like aux_get and
findname. Notably, config.setcpv() must be called with a Package
instance in order to ensure that it gets the metadata from the correct
repository.
|
|
|
|
|
|
| |
When overriding PORTDIR_OVERLAY, we can avoid "Location not set for
repository" messages if we include the original PORTDIR_OVERLAY paths
in the overridden setting.
|
|
|
|
|
| |
This enables controling the behaviour (creation and validation) per
repo, and while mildly ugly, refactors in the right direction.
|
| |
|
| |
|
| |
|
|
|
|
| |
This should improve repo-level support, for bug #370693.
|
|
|
|
|
|
|
| |
This prevents memory leaks via portdbapi.portdbapi_instances when the
module is reloaded. Also, there's no need for ebuild(1) to call
close_portdbapi_caches() since it's now handled automatically during
the reload.
|
| |
|
|
|
|
|
|
| |
This has been broken since the setcpv call (triggering metadata
generation) was added before it in commit
0b39d24bb8270e5c89eaddfd1f5a4181cf9e31d3.
|
|
|
|
| |
This makes it possible to override PORTAGE_TMPDIR.
|
|
|
|
|
| |
This is the same convention that bash uses for returncodes of
processes that are killed by signals.
|
|
|
|
|
|
|
|
|
| |
Since commit 75d3130fc8293fff68389b8fed44b8d47a0abe80, doebuild()
for the 'setup' phase triggers the actionmap_deps code path in order
to call the 'pretend' phase as a dependency. This path previously
assumed a portdbapi instance, which may not hold for some api consumers
such as entropy. Therefore, fix the code path to work with other dbapi
types.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
enhancements:
* The FEATURES variable is automatically synchronized upon modification.
* Modifications result in a permanent override that will cause the change
to propagate to the incremental stacking mechanism in config.regenerate().
This eliminates the need to call config.backup_changes() when FEATURES
is modified, since any overrides are guaranteed to persist despite calls
to config.reset().
This allows cleanup of all code that overrides FEATURES, and also allows
config.regenerate() to stack FEATURES such that special cases are not
needed for package.env handling inside config.setcpv().
|
|
|
|
|
| |
consumers. Once the relevant api changes are in a portage release with
stable keywords, make these warnings unconditional.
|
|
|
|
| |
"Appending /var/db/pkg to PORTDIR_OVERLAY..." treatment.
|
| |
|
| |
|
|
|
|
| |
PORTDIR_OVERLAY paths.
|
|
|
|
| |
reporting.
|
| |
|
| |
|
|
|
|
|
|
|
| |
this is signal hander now set automatically for subprocesses after the fork
in portage.process.spawn().
svn path=/main/trunk/; revision=15826
|
|
|
|
| |
svn path=/main/trunk/; revision=15824
|
|
|
|
|
|
|
| |
subprocesses by SIGPIPE (as emerge has for a long time). Thanks to Harald van
Dijk truedfx@g.o for this patch.
svn path=/main/trunk/; revision=15823
|
|
|
|
|
|
| |
TERM=dumb.
svn path=/main/trunk/; revision=15191
|
|
|
|
|
|
| |
going to be used by emerge to force color fetch output when appropriate.
svn path=/main/trunk/; revision=14529
|
|
|
|
|
|
| |
up temp files on tmpfs after build failures with --keep-going.
svn path=/main/trunk/; revision=14517
|
|
|
|
| |
svn path=/main/trunk/; revision=14426
|
|
|
|
| |
svn path=/main/trunk/; revision=14291
|
|
|
|
|
|
| |
(2to3-3.1 -f print -nw ${FILES})
svn path=/main/trunk/; revision=14290
|
|
|
|
|
|
| |
(2to3-3.1 -f except -nw ${FILES})
svn path=/main/trunk/; revision=14289
|
|
|
|
| |
svn path=/main/trunk/; revision=14187
|
|
|
|
|
|
| |
_unicode_encode() and _unicode_decode() where appropriate.
svn path=/main/trunk/; revision=13993
|
|
|
|
|
|
| |
experimental purposes and should not be enabled under normal circumstances.
svn path=/main/trunk/; revision=13175
|
|
|
|
| |
svn path=/main/trunk/; revision=13150
|
|
|
|
|
|
|
|
| |
ebuild atain in this case (even though $T/environment may already exist).
This should help avoid confusion by ensuring that the latest changes to
the ebuild/eclasses are reflected in the environment.
svn path=/main/trunk/; revision=13148
|