| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Synchronous waiting for status is not supported, since it would be
vulnerable to hitting the recursion limit when a large number of tasks
need to be terminated simultaneously, like in bug #402335.
|
| |
|
|
|
|
| |
The _keep_scheduling() template method is used instead.
|
| |
|
|
|
|
|
| |
The way we don't leave an leak a reference to the Scheduler instance
in the global EventLoop instance.
|
| |
|
|
|
|
|
| |
We can use iteration() instead, and _poll_loop's exit behavior doesn't
seem practical to emulate with glib.MainLoop.
|
|
|
|
|
| |
Since commit 4620d6aba1c5c10344e311585516ee43819b703c, the first
prefetcher is started as soon as it's added to the task queue.
|
|
|
|
|
|
|
| |
This is needed to compensate for the removal of _idle_schedule in
commit 8c1fcf5a9ba9fa4d406a4d0cc284fe73a84f5a63, so that the
Scheduler's task queues operate without needing their schedule methods
called inside Scheduler._schedule_tasks().
|
|
|
|
|
| |
This shouldn't be needed, since _schedule() should already be called
automatically when there are any relevant state changes.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Now PollScheduler will execute timeouts predictably, even when there
no IO events being generated. This allows the Scheduler's display
updates to be handled via timeout_add.
|
|
|
|
|
| |
This will be useful as a substitute for recursion, in order to avoid
hitting the recursion limit for bug #402335.
|
|
|
|
|
|
|
| |
Since commit a715b65f7bd36409c1283e6911265d1f4405ab7a, the Package.root
and RootConfig.root attributes refer to EROOT instead of ROOT.
Therefore, adjust display code so that EROOT is only displayed when
ROOT != "/".
|
| |
|
|
|
|
|
|
|
|
|
| |
This reverts the behavior change from commit
0cc174b6fc28feb26ea151d76f794e0ff2c2fa39, since Gentoo's council has
voted to revert it in their 20111213 meeting, as requested on the
gentoo-project mailing list:
http://archives.gentoo.org/gentoo-project/msg_4e282bb4e6ac2611de2a39171a803c48.xml
|
| |
|
| |
|
|
|
|
|
|
|
| |
Instead, finish the whole job using a copy of the currently running
instance. This allows us to avoid the complexities of emerge --resume,
such as the differences in option handling between different portage
versions, as reported in bug #390819.
|
| |
|
|
|
|
|
| |
This ensures that the clean phase will not run if the user interrupts
emerge before the build dir is locked.
|
| |
|
|
|
|
|
| |
Since --quiet-build is enabled be default, there's no need to have it
in the options dict except when it is enabled.
|
|
|
|
| |
This fixes a regression from the previous commit.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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 options disables creation of binary packages, no matter
what enabled it in the first place. See bug 386903.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it possible to disable the dynamic dependency updates that
FakeVartree performs by default.
WARNING: If --dynamic-deps is disabled, then it is necessary to
ensure that an alternative method is used to handle package moves
in dependencies of installed packages. Normally, this is handled
by FEATURES="fixpackages", which is enabled by default and may be
disabled via make.conf(5). Alternatively, in order to manually apply
package moves, run `emaint --fix moveinst` after each emerge --sync
operation (see emaint(1)).
|
| |
|
| |
|
|
|
|
|
|
| |
This avoids a case where the first prefetcher is discarded, causing
the second prefetcher to occupy the fetch queue before the first
fetcher has an opportunity to execute.
|
| |
|
|
|
|
|
|
| |
This should also fix bugs related to CompositeTask instances waiting
for queued tasks to start and not being properly terminated in this
case.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Since commit f07f8386e945b48358c11c121960e4833c539752, the first will
have to wait for later ones to fetch unless we start its prefetcher
first.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
This ensures that we account for EMERGE_LOG_DIR.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This should prevent FEATURES=parallel-install from interfering with
the fixes from bug #256616 and bug #259954.
|