| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
from being saved in environment.bz2.
|
|
|
|
| |
a workaround for bug #288863 in the stable branch.
|
|
|
|
|
|
| |
first check for non-empty $SANDBOX_LOG and signal unsuccessful exit
if necessary. This fixes an issue with phases being treated as
successful even when there were sandbox violations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
packages, and use it for evaluating conditional USE deps in atoms
passed via IPC to helpers like has_version and best_version.
Since the pickled object that contains the IPC command will no longer
contain USE, it should solve cases that have been reported in which
large USE strings trigger poor handling of non-blocking read in
pickle.load():
Traceback (most recent call last):
File "/usr/bin/emerge", line 43, in <module>
retval = emerge_main()
File "/usr/lib64/portage/pym/_emerge/main.py", line 1649, in emerge_main
myopts, myaction, myfiles, spinner)
File "/usr/lib64/portage/pym/_emerge/actions.py", line 437, in action_build
retval = mergetask.merge()
File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1033, in merge
rval = self._merge()
File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1349, in _merge
self._main_loop()
File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1498, in _main_loop
self._poll_loop()
File "/usr/lib64/portage/pym/_emerge/PollScheduler.py", line 139, in _poll_loop
handler(f, event)
File "/usr/lib64/portage/pym/_emerge/EbuildIpcDaemon.py", line 36, in _input_handler
obj = pickle.load(self._files.pipe_in)
File "/usr/lib64/python2.6/pickle.py", line 1370, in load
return Unpickler(file).load()
File "/usr/lib64/python2.6/pickle.py", line 858, in load
dispatch[key](self)
File "/usr/lib64/python2.6/pickle.py", line 1195, in load_setitem
value = stack.pop()
IndexError: pop from empty list
|
|
|
|
| |
workaround for portage-9999 users.
|
|
|
|
|
|
| |
ebuild.sh where appropriate:
* unpack()
* environment.bz2 compression
|
| |
|
| |
|
|
|
|
|
|
|
| |
When checking ${PIPESTATUS[@]} for extraction of tar files in unpack(),
use a new assert_sigpipe_ok() function which behaves the same as the
existing assert() function except that it tolerates pipe writers being
killed by SIGPIPE.
|
| |
|
|
|
|
|
|
| |
pre-built binaries. Paths listed here will be appended to each of
the other QA_* variables. Thanks to Diego Pettenò <flameeyes@g.o>
for the suggestion.
|
|
|
|
|
|
|
| |
environment, in order to prevent ebuilds from abusing it. In
preparation for that, export it as PORTAGE_FEATURES so that bashrc
users will be able to migrate any FEATURES conditional code to
use this alternative variable.
|
|
|
|
|
|
| |
is needlessly long.
* When calling helpers_die from a function, use ${FUNCNAME[0]} in
arguments instead of $0.
|
|
|
|
|
|
| |
with a minimal environment. This gives coverage to some of the ebuild
execution internals, like ebuild.sh, EbuildSpawnProcess, and
EbuildIpcDaemon.
|
|
|
|
|
| |
intermittent build failures in my stage builds. For testing purposes
set PORTAGE_IPC_DAEMON_ENABLE=1 to enable EbuildIpcDaemon.
|
|
|
|
|
|
| |
built/installed packages, since the config class doesn't currently provide
a way to access built/installed $USE that would work in all possible
scenarios.
|
|
|
|
|
| |
doesn't have to be passed to the daemon in has_version and
best_version calls.
|
|
|
|
| |
callback from executing.
|
|
|
|
| |
It avoids some errors during upgrade from older Portage versions.
|
| |
|
|
|
|
| |
ebuild.sh.
|
|
|
|
|
| |
This provides performance benefits and also avoids permissions issues with
FEATURES=userpriv.
|
|
|
|
|
|
|
| |
since it seems more reliable this way. This helps us avoid having
EbuildIpcDaemon need to send a kill signal (and triggering the
zombie message too). This is especially important for the die helper
which is called by other helpers for EAPI 4.
|
|
|
|
| |
EBUILD_EXIT_STATUS_FILE.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
the shebang of configure scripts when appropriate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows make to do its thing when using Portage in a development
workflow, although the change also exposes how ebuild clean doesn't
clear out the WORKDIR.
TEST=`rm -rf /build/$board/tmp/portage/chromeos-base/kernel-0.0.1 &&
[ -e /build/$board/tmp/portage/chromeos-base/kernel-0.0.1/.unpacked ] &&
rm /build/$board/tmp/portage/chromeos-base/kernel-0.0.1/.unpacked &&
FEATURES=keepwork ebuild-$board kernel-0.0.1.ebuild install`
Then modify some of the source (preferably in the git repository rather
than the WORKDIR).
`[ -e /build/$board/tmp/portage/chromeos-base/kernel-0.0.1/.unpacked ] &&
rm /build/$board/tmp/portage/chromeos-base/kernel-0.0.1/.unpacked &&
FEATURES=keepwork ebuild-$board kernel-0.0.1.ebuild install &&`
On the second ebuild operation, make should be able to tell what
exactly, or if nothing at all, has changed, and rebuild only the
necessary object files.
http://codereview.chromium.org/2922001
|
|
|
|
|
|
| |
3rd argument conditional on EAPI in order to ensure backward
compatibility. This reverts the behavior change from commit
a05bba76435d94407fd25549d0552902962baf62 for EAPI 0, 1, 2, and 3.
|
| |
|
| |
|
|
|
|
| |
check-implicit-pointer-usage.py.
|
|
|
|
|
| |
is used to explicitly run the test phase along with other
phases.
|
|
|
|
| |
EAPI 4 instead of 3.
|
|
|
|
|
|
|
| |
Support loading per-package bashrc files from the /etc/portage/env
directory. The invidual files should reside in a directory matching
${CATEGORY}, with names matching ${PN}, ${PN}:${SLOT}, ${P} and/or ${PF}
(which are applied in that order).
|
| |
|
| |
|
| |
|
|
|
|
| |
svn path=/main/trunk/; revision=15830
|
|
|
|
|
|
| |
phase hooks, in order to migrate away from global scope useq() calls.
svn path=/main/trunk/; revision=15829
|
|
|
|
|
|
| |
trust tar exist status alone (reverts r15820 and r15821).
svn path=/main/trunk/; revision=15827
|
|
|
|
|
|
| |
when unpacking tar files.
svn path=/main/trunk/; revision=15820
|
|
|
|
|
|
| |
virtual package.
svn path=/main/trunk/; revision=15349
|
|
|
|
| |
svn path=/main/trunk/; revision=15348
|
|
|
|
|
|
| |
(when the EAPI is first known) rather than for each phase.
svn path=/main/trunk/; revision=15149
|
|
|
|
| |
svn path=/main/trunk/; revision=15147
|