| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This simplifies the interface, avoiding the need for hardcoded indexes
and making it easy to add new attributes.
|
|
|
|
|
|
|
| |
This reduces memory consumption by approximately 30%, by replacing
mutable set instances with arrays, tuples, and frozensets where
appropriate. Also, identical frozenset instances are shared when
available.
|
|
|
|
|
| |
Thanks to Sven Vermeulen <sven.vermeulen@siphos.be> for the initial
patch posted on bug #375835.
|
|
|
|
|
|
| |
Before it would only include the SLOT in the atom if there were
multiple slots installed. However, taht could lead to unwanted upgrades
as reported in bug #338959. Therefore, always create SLOT atoms.
|
|
|
|
|
| |
If there are no non-excluded providers then there's no need to search
for satisfied consumers.
|
|
|
|
|
|
| |
Currently, we never pass in more that one package via the
exclude_providers argument, so we never trigger the flaw in the logic
that this fixes.
|
| |
|
|
|
|
| |
This avoids a redundant pordbapi.findname() call.
|
|
|
|
|
|
| |
This removes a very subtle difference in --noreplace package selection
logic which is not very useful and triggers strange package selection
choices in some cases, as reported in bug #375571.
|
|
|
|
|
|
| |
This should also fix bugs related to CompositeTask instances waiting
for queued tasks to start and not being properly terminated in this
case.
|
|
|
|
|
|
| |
This will fix bug #289180 by making LinkageMapELF.findconsumers()
exclude consumers from the results in cases when they are satisfied by
an alternative provider of the required soname.
|
|
|
|
|
|
|
| |
This reverts behavior from bug #375331 (commit
f07f8386e945b48358c11c121960e4833c539752) for cases in which --jobs is
greater than 1. We can add a separate --fetch-jobs option later, but
for now, this preserves previous behavior for --jobs > 1.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is analogous to commit f07f8386e945b48358c11c121960e4833c539752
for bug #375331, but for fetching from binhosts.
|
|
|
|
|
|
|
| |
Since commit f07f8386e945b48358c11c121960e4833c539752, it was possible
for EbuildBuild to wait on the fetch queue even in cases in which all
required files had been previously fetched. Now this case is optimized
to skip the fetch queue, as discribed in bug #375331, comment #2.
|
|
|
|
|
|
| |
Since commit f07f8386e945b48358c11c121960e4833c539752, the first will
have to wait for later ones to fetch unless we start its prefetcher
first.
|
|
|
|
| |
This will fix bug #375331.
|
| |
|
| |
|
| |
|
|
|
|
| |
This allows us to avoid parsing the Manifest twice.
|
|
|
|
|
| |
When we call digestgen(), it can regenerate our distfiles digests and
we don't wan to cache stale values in this case.
|
|
|
|
| |
This allows us to avoid parsing the Manifest twice.
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 62712db56bb863b4eb0a9d9c52e7b2c3ad38df66.
This code already defaulted to the allow-missing-manifests behavior,
since the fetch() allow_missing_digests argument default is true. By
making the argument conditional on allow-missing-manifests, it changed
the behavior in the default case where allow-missing-manifests is
disabled.
|
|
|
|
|
| |
These belong in the blacklist, in order to avoid potential interference
from the calling environment.
|
|
|
|
|
| |
This should fix "Insufficient data for checksum verification" errors
triggered by ebuild --skip-manifest.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Since StringIO.StringIO fallback was removed in commit
5df96179611ce0e98727945b1800b43daccedfc2, we can rely on
io.StringIO.getoutput() to return unicode, so there's no
need to call _unicode_decode on the result.
|
|
|
|
|
|
|
|
| |
Since the io module in python-2.6 was broken when threading was
disabled, we needed to fall back from io.StringIO to StringIO.StringIO
in this case (typically just for Gentoo's stage1 and stage2 tarballs).
Now that python-2.7 is stable in stages and we rely on io.open() being
available, we can also rely on io.StringIO being available.
|
| |
|
|
|
|
|
| |
These permissions should be compatible with our default logrotate
config as discussed in bug 374287.
|
| |
|
|
|
|
|
| |
This is a major regression that has been triggering lots of complaints
about emerge --keep-going.
|
|
|
|
|
| |
This fixes permission issues with category subdirectories created for
FEATURES=split-elog.
|
|
|
|
|
| |
The gid of PORT_LOGDIR is copied to all subdirectories, along with
0x2070 mode bits if present.
|
|
|
|
|
|
| |
Also, suppress this maintainer info from going to stdout since it's
intended for the log and it doesn't necessarily need to be visible
elsewhere. This will fix bug #374809.
|
|
|
|
|
|
| |
If there is insufficient permission to use PORT_LOGDIR or the required
subdirectory, warn instead of raising an exception. Also, fall back to
using $T/build.log as a last resort.
|