| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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
|
|
|
|
| |
svn path=/main/trunk/; revision=15143
|
|
|
|
| |
svn path=/main/trunk/; revision=15130
|
|
|
|
| |
svn path=/main/trunk/; revision=15098
|
|
|
|
|
|
| |
ebuild phases, and only filter them for binary and installed packages.
svn path=/main/trunk/; revision=15096
|
|
|
|
|
|
| |
2.
svn path=/main/trunk/; revision=15057
|
|
|
|
| |
svn path=/main/trunk/; revision=15035
|
|
|
|
| |
svn path=/main/trunk/; revision=15034
|
|
|
|
|
|
| |
current EAPI.
svn path=/main/trunk/; revision=15031
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
filter_readonly_variables() but don't mark them readonly for now since some
ebuilds/eclasses try to assign EROOT (such as kde4-base_pkg_setup) which
causes the whole bash shell to exit like this:
>>> Extracting info
* CPV: kde-base/oxygen-icons-4.3.4
* REPO: gentoo
* USE: elibc_glibc kernel_linux test userland_GNU x86
/var/tmp/portage/kde-base/oxygen-icons-4.3.4/temp/environment: line 2781: EROOT: readonly variable
Also, add ED to the environment blacklist.
svn path=/main/trunk/; revision=15030
|
|
|
|
|
|
|
|
|
|
|
| |
EROOT available to the ebuild environment, and updates the manpage
accordingly. EPREFIX is hardwired to the empty string, and not
configurable. For that, the prefix branch should be used for now.
This should satisfy the requirements for EAPI=3.
svn path=/main/trunk/; revision=15024
|