| 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 reduces the probability of users encountering issues related to
package moves when they disable --dynamic-deps, and --package-moves=n
can be set in EMERGE_DEFAULT_OPTS if package moves need to be
temporarily avoided for some reason.
|
|
|
|
| |
_global_updates().
|
| |
|
| |
|
|
|
|
|
| |
if the world file and vdb are slighly out of sync wrt package moves.
* Write world file updates at the earliest opportunity.
|
|
|
|
|
|
| |
efficient this way, and this function can't be called separately for each
repo if /etc/portage is under CONFIG_PROTECT (because it would produce
separate updated files for each repo).
|
|
|
|
| |
since that's all that the calling code currently needs.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
for all of the following cases:
* package is missing repository metadata
* package has repository metadata, but the source repository does not
have a profiles/updates/ directory
* package has repository metadata, but the source repository is not
currently accessible via PORTDIR_OVERLAY
|
| |
|
| |
|
|
|
|
| |
most efficient to process all repos at once.
|
|
|
|
|
|
| |
As a backwards-compatibility measure, if a particular repository doesn't
come with an 'updates' directory, fallback to updates from
dbapi.porttree_root.
|
|
|
|
|
| |
Update dbentries only when the repository the package comes from matches
the repository update comes from.
|
|
|
|
|
|
|
| |
Support reading repository-wide update files. Apply them as long as the
'repository' for vardb entry matches the repository update is
originating from. For world and configuration files, use the best vardb
match.
|
| |
|
|
|
|
|
|
|
|
| |
bail out with an error message in this case which suggests to instead use
emaint --fix movebin and/or moveinst. This prevents useless/ugly global
updates messages that flood the terminal when ROOT != "/".
svn path=/main/trunk/; revision=15728
|
|
|
|
|
|
|
| |
packages (getbinpkgs=0), and fix binarytree.populate() to behave properly
when called more than once.
svn path=/main/trunk/; revision=15487
|
|
svn path=/main/trunk/; revision=15475
|