| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It doesn't behave as intended for $ED which has a trailing slash.
|
|
|
|
|
|
| |
This uses a python-based chpathtool implementation which is intended to
be compatible with the C-based implemenation that the prefix branch
uses.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
This fixes an interaction between the code from commits
9ce6da43ab90c4dab97ebf3b8339e5dbc113a0a8 and
cbe44d92ff13b8a22f5b4215b73078ce600c6bf4, so that we don't discard
matches that are identical except for differnces in upper/lower case.
|
|
|
|
|
|
| |
The fixes some cases where emerge.log would show that depclean was
unsuccessful when it was really successful but there was nothing to
remove.
|
|
|
|
|
|
| |
Looping fixes EbuildMetadataPhase failures for ebuilds that produce
more than 4096 bytes of metadata, broken since commit
b432a1b3051d91546649e8f3190675767461d8e8.
|
| |
|
|
|
|
|
|
| |
Similar to commit b432a1b3051d91546649e8f3190675767461d8e8, don't use
unecessary file objects. It also happens that these changes fix
compatibility issues with PyPy.
|
|
|
|
|
|
| |
There's no need for a file object, and file objects introduce
complexity that can lead to bugs as mentioned in bug 337465 comment 31,
so use os.read() directly on the file descriptor.
|
| |
|
|
|
|
|
|
|
| |
This fixes a regression since commit
57cc4e3e8991e7c4394d1dff7698aa62ed2a286b, which make a faulty
assumption that the digraph contained all of the edges contained in
parent_atoms.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is a regression from commit
69d7f169ba2e27cf56746791331c63a019357100, reported in bug #390893.
|
|
|
|
|
| |
There's no need to do this anymore, because we don't restart since
commit d3f704a425a50b5cfa997a25866929b30f1b7d0f.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
See discussion on the gentoo-dev mailing list:
http://archives.gentoo.org/gentoo-dev/msg_4f0401066abe2dc04458a952ac2a17bd.xml
|
|
|
|
|
| |
None of these cases should raise KeyError, but use get(REQUIRED_USE)
anyway to emphasize that care must be taken.
|
|
|
|
| |
This goes with commit a0961708ced50c90497811058eda6f4513d2986d.
|
| |
|
|
|
|
| |
--info actions.
|
| |
|
|
|
|
|
|
|
| |
It should be safe to assume that REQUIRED_USE is satisfied if the
package is built, so it's a waste to save it. Also, fix code which
assumes that built Package instances have a REQUIRED_USE key in their
metadata.
|