| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This takes EPREFIX from the env argument and uses it when joining all
paths. Also, ldconfig calls are disabled when EPREFIX is non-empty,
since it's inappropriate to update the global /etc/ld.so.cache in this
case.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This simply checks of $PORTAGE_BUILDDIR/.${EBUILD_PHASE%e}ed and skips
the phase like ebuild.sh would. It preserves a special case for the
install phase with FEATURES=noauto, so that dyn_install in ebuild.sh
continues to work the same for this case.. Also, note that commit
ae9b6cb513c7b29376caecf3b4e52aac452e2b93 preserves the automatic
"recreating WORKDIR" behavior that used to be implemented in
dyn_unpack.
|
|
|
|
|
|
|
|
|
| |
When the unpack phase is already marked as complete, it's wasteful to
check distfiles digests. In order to avoid this, we have to migrate the
distfiles/workdir timestamp comparisons from ebuild.sh to doebuild.py,
so that doebuild always knows when unpack will be triggered. This also
allows us to eliminate code in dyn_unpack that duplicated dyn_clean,
actually call dyn_clean instead.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Right now, the --rebuild-if-* flags only rebuild packages that are used at
both run-time and build-time. This doesn't help for packages that are used
only at build-time (for example, static libaries).
Rebuilding packages whenever a build-time dependency is changed is easier to
understand and explain, and it handles all cases correctly.
BUG=chromium-os:15517
TEST=Run emerge test suite.
Change-Id: Iae8dab24e8acb6625bc1a0ce41862e90b232eb84
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Python supports skipped tests since 2.7, but we'll implement support
ourselves for python 2.6 compatibility. This is a simple extension of
the todo support that we have already implemented.
|
| |
|
|
|
|
|
| |
DeprecationWarning is suppressed by default since Python 2.7, so it's
a good idea to explicitly enable it for tests.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
removed when support for older versions of Python is removed.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This variable could cause interference with the ebuild environment and
portage shell code, like in bug 370085.
|
|
|
|
|
|
|
|
|
|
|
| |
If PORT_LOGDIR is writable by the portage group but its uid is not
portage_uid, then set the uid to portage_uid if we have privileges to
do so, and also copy the uid to the logfile. This fixes logrotate
chown failures during the compression phase, when it attempts to copy
the uid from the logfile to a temp file. With the "su portage portage"
directive and logrotate-3.8.0, logrotate's chown call during the
compression phase will only succeed if the log file's uid is
portage_uid.
|
|
|
|
| |
This should fix some cases of bug 378187.
|
|
|
|
|
|
| |
This adds docinto, docompress, fowners and fperms to the
variable.usedwithhelpers check. Notably absent is dosed since that
supports mixed input. This will fix bug #377303.
|
| |
|
|
|
|
|
|
|
|
| |
Since this is considered a "legacy" feature by PMS 5.2.7, there
shouldn't be any need to support it anymore. Profiles can use
package.mask to get similar results, and package.mask additionally
allows for comments which are conveniently displayed by emerge. This
will fix bug #377907.
|
|
|
|
| |
This will fix bug #378403.
|
| |
|
|
|
|
|
| |
Treat any directory named "info" as a candidate here, since it might
have been in INFOPATH previously even though it may not be there now.
|
|
|
|
|
|
| |
These files are generated by emerge, so we need to remove them
when they are the only thing left in the directory. This will fix
bug #323213.
|
|
|
|
|
| |
This should prevent strange output buffering/order issues reported when
piping output to head.
|
|
|
|
|
|
| |
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 prevents some more false alarms from commit
4bb08136f073024c5d31dceb1618b6f4e7246369.
|
| |
|
|
|
|
|
|
|
| |
The error message about preserved symlinks, from commit
4bb08136f073024c5d31dceb1618b6f4e7246369, should only be triggered in
cases when the package being unmerged has the given path listed as a
symlink in its CONTENTS.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, it was possible to unmerge a symlink to a directory, such that
files installed via the path of the symlink could become inaccessible
via that path (and also making it impossible to unmerge them via that
path).
Now, the symlink will only be unmerged if the directory that it points
to only contains regular files which are all being unmerged. In any
other case, the symlink will be preserved and an eerror log message
will record the event. This will give the user an opportunity to take
further action if they deem it necessary, and such symlink preservation
will not be silent as it was reported in bug #326685, comment #3.
|