| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This ensures compatibility with previous portage versions for cases in
which the user has added PORTDIR to PORTDIR_OVERLAY as a means to modify its
priority relative to overlays when selecting ebuilds.
|
| |
|
| |
|
|
|
|
|
|
| |
This is necessary since portage probes functions in globals() and
treats functions it finds as commands. Also, use lazy import to
minimize global scope imports.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Something like this was requested in bug #157357. Now that Gentoo has
migrated all virtuals to GLEP 37 new-style virtuals, this kind of
function may be helpful in order to resolve the currently installed
provider of a particular virtual in scripts like bootstrap.sh.
Usage:
portageq expand_virtual <root> <atom>
Returns a \n separated list of atoms expanded from a
given virtual atom, excluding blocker atoms. Satisfied
virtual atoms are not included in the output, since
they are expanded to real atoms which are displayed.
Unsatisfied virtual atoms are displayed without
any expansion. The "match" command can be used to
resolve the returned atoms to specific installed
packages.
Example input/output:
$ portageq expand_virtual / virtual/jre
=dev-java/sun-jdk-1.6.0*
$ portageq expand_virtual / virtual/jre:1.5
dev-java/gcj-jdk
$ portageq expand_virtual / virtual/package-manager
sys-apps/portage
$ portageq expand_virtual / virtual/libc
sys-libs/glibc:2.2
$ portageq expand_virtual / virtual/os-headers
sys-kernel/linux-headers:0
|
|
|
|
|
|
| |
We already have the Eapi4GoneVars check for AA and KV which were
removed in EAPI 4, so we can re-use it to disallow EMERGE_FROM.
This will fix bug #368865.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is required in order for dep_zapdeps to work as intended for
solving cases of bug #264434 in which there is an installed
package that may need to be uninstalled in order to resolve blockers.
It fixes a failure to resolve blockers when attempting to replace
media-video/ffmpeg with media-video/libav (symptom is similar to
bug #339164, but with new-style virtual instead of old-style PROVIDE
virtual).
|
| |
|
| |
|
|
|
|
| |
This will fix bug #369383.
|
| |
|
|
|
|
| |
This output is similar to that produced by unmerge().
|
|
|
|
|
| |
We don't want to return the returncode directly from the
subprocess. Return self.returncode instead.
|
| |
|
|
|
|
|
|
| |
Since we hold a lock, this is a good opportunity to flush the cache.
Note that this will only flush the cache periodically in the main
process when _aux_cache_threshold is exceeded.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The 2.1.9 branch already does the same thing since commit
65736474c0d70cb10ff1290b3787b61d8a502aed.
|
| |
|
|
|
|
|
| |
This is required for the doebuild_environment() call. Also, set
builddir_locked = True when appropriate.
|
|
|
|
|
|
| |
Every package install must have a unique counter, since a slotmove
update can move two packages into the same SLOT and in that case it's
important that both packages have different COUNTER metadata.
|
|
|
|
| |
This will fix bug #368725.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also, fix calling code to handle InvalidLocation exceptions.
|
| |
|
| |
|
|
|
|
|
| |
We don't have any code that checks the writedict return value, so we'd
better raise an exception if it fails.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
If the corresponding unbuilt ebuild has a different EAPI than the
installed instance, then we want to preserve the EAPI meatadata from
the installed instance.
|
| |
|
|
|
|
| |
This will fix bug #368429.
|
| |
|
|
|
|
| |
Also, add to comments about ebuild-locks.
|
| |
|
|
|
|
|
| |
This fixes breakage from commit
f0f1bbe8fa9d3f698cbe529d2a11eec1ce437119.
|
| |
|
|
|
|
|
|
|
|
| |
This fixes another ebuild-locks issue like the one fixed in commit
a81460175a441897282b0540cefff8060f2b92dc, but this time we use a
subprocess to ensure that the ebuild-locks for pkg_prerm and
pkg_postrm do not interfere with pkg_setup ebuild-locks held by
the main process.
|
|
|
|
|
|
|
|
| |
All EAPI dependent code comes last, so that essential
variables like PORTAGE_BUILDDIR are still initialized even in
cases when UnsupportedAPIException needs to be raised, which
can be useful when uninstalling a package that has corrupt
EAPI metadata.
|