| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
sign). (trunk r9429)
svn path=/main/branches/2.1.2/; revision=9430
|
|
|
|
|
|
| |
cannot match the required non-alphanumeric group. (trunk r9421)
svn path=/main/branches/2.1.2/; revision=9422
|
|
|
|
|
|
| |
names that contain more than one non-alphanumeric character. (trunk r9419)
svn path=/main/branches/2.1.2/; revision=9420
|
|
|
|
|
|
|
| |
exclude variable names that begin with a digit or that contain any
non-alphanumeric characters that are not be supported by bash. (trunk r9416)
svn path=/main/branches/2.1.2/; revision=9417
|
|
|
|
|
|
|
| |
with names containing a hyphen since bash does not allow them.
(trunk r9402)
svn path=/main/branches/2.1.2/; revision=9403
|
|
|
|
|
|
|
| |
of egrep since apparently it's compatible in this case. Thanks to
igli for this. (trunk r9279)
svn path=/main/branches/2.1.2/; revision=9305
|
|
|
|
|
|
| |
to igli for suggesting. (trunk r9278)
svn path=/main/branches/2.1.2/; revision=9304
|
|
|
|
|
|
|
| |
installation phases need to pass some variables to
uninstallation phases. (trunk r9281)
svn path=/main/branches/2.1.2/; revision=9282
|
|
|
|
|
|
| |
QA Notice. (trunk r9249)
svn path=/main/branches/2.1.2/; revision=9250
|
|
|
|
|
|
|
|
|
|
|
| |
of false positives (bug #207104) and its hard to parse bash
- Use QA_INTERCEPTORS in ebuild.sh to implement a runtime
'QA Notice' when autotools is called directly
trunk r9235
svn path=/main/branches/2.1.2/; revision=9247
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=9246
|
|
|
|
|
|
|
|
|
| |
out of a subshell since FreeBSD and prefix users have reported
apparent corruption of the PATH environment variable that triggers
calls to the wrong version of sed (one that does not support the
-r option). (trunk r9193:9195)
svn path=/main/branches/2.1.2/; revision=9196
|
|
|
|
|
|
| |
config.guess and config.sub. (trunk r9162)
svn path=/main/branches/2.1.2/; revision=9171
|
|
|
|
|
|
| |
are in sync with the current NOCOLOR setting. (trunk r9158)
svn path=/main/branches/2.1.2/; revision=9170
|
|
|
|
|
|
| |
we never want to save of reload it. (trunk r9147)
svn path=/main/branches/2.1.2/; revision=9148
|
|
|
|
|
|
| |
(trunk r9145)
svn path=/main/branches/2.1.2/; revision=9146
|
|
|
|
|
|
|
| |
is needed for compatibility with environment.bz2 files generated
by paludis. (trunk r9137)
svn path=/main/branches/2.1.2/; revision=9138
|
|
|
|
|
|
|
| |
avoid a situation where attempts to read arbitrary files trigger
sandbox violations. (trunk r9085)
svn path=/main/branches/2.1.2/; revision=9086
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add EBUILD_FORCE_TEST to the environment whitelist and filter
it from the saved environment in save_ebuild_env().
* Tweak logic inside the ebuild command and config.regenerate()
so that EBUILD_FORCE_TEST works even in odd cases like when
USE=test is masked.
* Only make FEATURES=test map to USE=test when "test" is
actually in IUSE.
* Remove USE=test from the set of implicit IUSE so that useq()
calls in ebuild.sh properly generate a QA Notice when "test"
is missing from IUSE.
(trunk r9063:9065)
svn path=/main/branches/2.1.2/; revision=9076
|
|
|
|
|
|
|
|
| |
This will load the ${T}/environment file if available and then
source ${EBUILD} to overwrite any functions that have changed.
(trunk r9051 and r9062)
svn path=/main/branches/2.1.2/; revision=9068
|
|
|
|
|
|
| |
since that's the only time it's valid for now. (trunk r8951)
svn path=/main/branches/2.1.2/; revision=8952
|
|
|
|
|
|
|
|
| |
for use by the QA check that's built into useq(). This allows
the IUSE logic for this check to be isolated in the python
code. (trunk r8945)
svn path=/main/branches/2.1.2/; revision=8948
|
|
|
|
|
|
|
|
|
|
|
| |
want to modify it via bashrc to enable things like splitdebug
and installsources for specific packages. They should be able
to modify it in pre_pkg_setup() and have it persist all the
way through the install phase. However, if FEATURES exist
inside environment.bz2 then they should be overridden by
current settings. (trunk r8909)
svn path=/main/branches/2.1.2/; revision=8910
|
|
|
|
|
|
|
|
|
|
| |
${T}/environment it's a bit tricky because we have to temporarily
disable sandbox since the SANDBOX_{DENY,READ,PREDICT,_WRITE} values
we've just loaded may be unusable (triggering in spurious sandbox
violations) until we've merged them with our current values.
(trunk r8905:8907)
svn path=/main/branches/2.1.2/; revision=8908
|
|
|
|
|
|
|
| |
paths that start with ${DISTDIR} and die an appropriate error
message. Thanks to grobian for this patch. (trunk r8896)
svn path=/main/branches/2.1.2/; revision=8903
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
instead of removing it completely.
* Bug #202068 - In order to filter unwanted variable assignments out
of the bash environment, use a filter-bash-environment.py script
that behaves similar to egrep -v except that it leaves bash here-
documents intact.
* Use the sed -r option to enable extended regular expressions so that
commonly used characters like (, ), and + don't have to be escaped.
(trunk r8890:8893)
svn path=/main/branches/2.1.2/; revision=8899
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as PORTAGE_BINPKG_FILE in order to give bashrc users an opportunity
to do various things such as remove binary packages after they're
installed.
* Add a note in ebuild.sh explaining why hardcoded bash lists are
needed for backward compatibility with <portage-2.1.4 since they
assume that a newly installed version of ebuild.sh will work for
pkg_postinst, pkg_prerm, and pkg_postrm when portage is upgrading
itself.
(trunk r8878)
svn path=/main/branches/2.1.2/; revision=8881
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8860
|
|
|
|
|
|
| |
environment in preprocess_ebuild_env(). (trunk r8857)
svn path=/main/branches/2.1.2/; revision=8858
|
|
|
|
|
|
|
| |
and let it run to the bottom of ebuild.sh just like the other
phases. (trunk r8852)
svn path=/main/branches/2.1.2/; revision=8856
|
|
|
|
|
|
|
|
| |
SANDBOX_{DENY,PREDICT,READ,WRITE} between all phases,
except when the environment comes directly from
environment.bz2. (trunk r8853)
svn path=/main/branches/2.1.2/; revision=8854
|
|
|
|
|
|
|
| |
generation with the conditional that triggers distcc and
ccache FEATURES setup. (trunk r8833)
svn path=/main/branches/2.1.2/; revision=8834
|
|
|
|
|
|
|
| |
if called during the "depend" phase with a flag that uses
IUSE defaults. (trunk r8805)
svn path=/main/branches/2.1.2/; revision=8806
|
|
|
|
|
|
|
| |
sandbox's bashrc sources /etc/profile which unsets ROOTPATH,
so we have to back it up and restore it. (trunk r8775:8777)
svn path=/main/branches/2.1.2/; revision=8778
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8775
|
|
|
|
|
|
| |
side then restore it on the bash side. (trunk r8768)
svn path=/main/branches/2.1.2/; revision=8769
|
|
|
|
|
|
|
| |
variables that are in environment.bz2 so that they are
available for use by tools such as epm. (trunk r8765)
svn path=/main/branches/2.1.2/; revision=8766
|
|
|
|
|
|
|
| |
'source /etc/profile' which can interfere with the build
environment by modifying our PATH. (trunk r8761)
svn path=/main/branches/2.1.2/; revision=8762
|
|
|
|
|
|
|
|
|
| |
environment from the calling environment. This makes it possible
for the build to unset a variable that was inherited from the
calling environment, and the variable will remain unset between
phases. (trunk r8752:8755)
svn path=/main/branches/2.1.2/; revision=8756
|
|
|
|
|
|
| |
PORTAGE_PYM_PATH works. (trunk r8745)
svn path=/main/branches/2.1.2/; revision=8746
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8730
|
|
|
|
|
|
| |
return early when necessary. (trunk r8718)
svn path=/main/branches/2.1.2/; revision=8719
|
|
|
|
|
|
|
|
|
|
| |
to accomodate this, create a PORTAGE_MUTABLE_FILTERED_VARS list for
variables that portage sets but doesn't mark readonly. In order to
prevent changed values from causing unexpcted interference, they are
filtered out of the environment when it is saved or loaded (any
mutations do not persist). (trunk r8708)
svn path=/main/branches/2.1.2/; revision=8709
|
|
|
|
|
|
| |
necessary. (trunk r8700)
svn path=/main/branches/2.1.2/; revision=8701
|
|
|
|
|
|
|
| |
* Fix dyn_clean() to clean the status file and return early when appropriate.
(trunk r8692)
svn path=/main/branches/2.1.2/; revision=8693
|
|
|
|
|
|
| |
attempting to use it. (trunk r8686)
svn path=/main/branches/2.1.2/; revision=8687
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
exits unexpectedly. This is type of behavior is known
to be triggered by things such as failed variable
assignments (bug #190128) or bad substitution errors
(bug #200313).
We use a EBUILD_EXIT_STATUS_FILE environment variable
to specify a file that the shell code is supposed to
create when it exits in a normal manner. If the file
does not get created like it's supposed to be then we
can conclude that the shell has exited in some
unexpected way.
(trunk r8682)
svn path=/main/branches/2.1.2/; revision=8684
|
|
|
|
|
|
|
| |
"${T}/environment" does not exist, except for "clean"
and "depend" phases. (trunk r8680)
svn path=/main/branches/2.1.2/; revision=8681
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8675
|
|
|
|
|
|
|
|
| |
save_ebuild_env() to config.environ().
* Add EMERGE_FROM to the READONLY_PORTAGE_VARS list.
(trunk r8670)
svn path=/main/branches/2.1.2/; revision=8671
|