| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
svn path=/main/trunk/; revision=9195
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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). An example of what users have observed:
>>> Source compiled.
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
Traceback (most recent call last):
File "/usr/lib/portage/bin/filter-bash-environment.py", line 51, in <module>
compile_egrep_pattern(args[0]), file_in, file_out)
File "/usr/lib/portage/bin/filter-bash-environment.py", line 34, in filter_bash_environment
file_out.write(line)
IOError: [Errno 32] Broken pipe
svn path=/main/trunk/; revision=9194
|
|
|
|
|
|
| |
config.guess and config.sub.
svn path=/main/trunk/; revision=9162
|
|
|
|
|
|
| |
are in sync with the current NOCOLOR setting.
svn path=/main/trunk/; revision=9158
|
|
|
|
|
|
| |
we never want to save of reload it.
svn path=/main/trunk/; revision=9147
|
|
|
|
| |
svn path=/main/trunk/; revision=9145
|
|
|
|
|
|
|
| |
is needed for compatibility with environment.bz2 files generated
by paludis.
svn path=/main/trunk/; revision=9137
|
|
|
|
|
|
|
| |
avoid a situation where attempts to read arbitrary files trigger
sandbox violations.
svn path=/main/trunk/; revision=9085
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
svn path=/main/trunk/; revision=9064
|
|
|
|
|
|
| |
call, even if "${T}"/environment happens to exist for some reason.
svn path=/main/trunk/; revision=9062
|
|
|
|
|
|
|
| |
This will load the ${T}/environment file if available and then
source ${EBUILD} to overwrite any functions that have changed.
svn path=/main/trunk/; revision=9051
|
|
|
|
|
|
| |
since that's the only time it's valid for now.
svn path=/main/trunk/; revision=8951
|
|
|
|
|
|
|
|
| |
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.
svn path=/main/trunk/; revision=8945
|
|
|
|
|
|
|
|
|
|
|
| |
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.
svn path=/main/trunk/; revision=8909
|
|
|
|
| |
svn path=/main/trunk/; revision=8907
|
|
|
|
|
|
|
|
|
| |
${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.
svn path=/main/trunk/; revision=8906
|
|
|
|
|
|
|
| |
paths that start with ${DISTDIR} and die an appropriate error
message. Thanks to grobian for this patch.
svn path=/main/trunk/; revision=8896
|
|
|
|
|
|
| |
commonly used characters like (, ), and + don't have to be escaped.
svn path=/main/trunk/; revision=8893
|
|
|
|
|
|
|
|
| |
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.
svn path=/main/trunk/; revision=8892
|
|
|
|
|
|
| |
instead of removing it completely.
svn path=/main/trunk/; revision=8891
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
svn path=/main/trunk/; revision=8878
|
|
|
|
| |
svn path=/main/trunk/; revision=8859
|
|
|
|
|
|
| |
environment in preprocess_ebuild_env().
svn path=/main/trunk/; revision=8857
|
|
|
|
|
|
|
|
| |
SANDBOX_{DENY,PREDICT,READ,WRITE} between all phases,
except when the environment comes directly from
environment.bz2.
svn path=/main/trunk/; revision=8853
|
|
|
|
|
|
|
| |
and let it run to the bottom of ebuild.sh just like the other
phases.
svn path=/main/trunk/; revision=8852
|
|
|
|
|
|
|
| |
generation with the conditional that triggers distcc and
ccache FEATURES setup.
svn path=/main/trunk/; revision=8833
|
|
|
|
|
|
|
| |
if called during the "depend" phase with a flag that uses
IUSE defaults.
svn path=/main/trunk/; revision=8805
|
|
|
|
|
|
|
| |
sandbox's bashrc sources /etc/profile which unsets ROOTPATH,
so we have to back it up and restore it.
svn path=/main/trunk/; revision=8776
|
|
|
|
| |
svn path=/main/trunk/; revision=8774
|
|
|
|
|
|
| |
side then restore it on the bash side.
svn path=/main/trunk/; revision=8768
|
|
|
|
|
|
|
| |
variables that are in environment.bz2 so that they are
available for use by tools such as epm.
svn path=/main/trunk/; revision=8765
|
|
|
|
|
|
|
| |
'source /etc/profile' which can interfere with the build
environment by modifying our PATH.
svn path=/main/trunk/; revision=8761
|
|
|
|
| |
svn path=/main/trunk/; revision=8755
|
|
|
|
|
|
|
|
|
| |
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.
svn path=/main/trunk/; revision=8754
|
|
|
|
|
|
|
|
|
|
|
|
| |
the python side. The python will be able to use it's awareness
of the ${T}/environment to decide what type of ebuild environment
should be generated. For example, if the ebuild environment
should be able to unset variables that have been inherited from
the calling environment, the existence of ${T}/environment
will indicate that the ebuild environment should be isolated from
the calling environment.
svn path=/main/trunk/; revision=8753
|
|
|
|
|
|
| |
PORTAGE_PYM_PATH works.
svn path=/main/trunk/; revision=8745
|
|
|
|
| |
svn path=/main/trunk/; revision=8729
|
|
|
|
|
|
| |
return early when necessary.
svn path=/main/trunk/; revision=8718
|
|
|
|
|
|
|
|
|
|
| |
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).
svn path=/main/trunk/; revision=8708
|
|
|
|
|
|
| |
necessary.
svn path=/main/trunk/; revision=8700
|
|
|
|
|
|
| |
* Fix dyn_clean() to clean the status file and return early when appropriate.
svn path=/main/trunk/; revision=8692
|
|
|
|
|
|
| |
attempting to use it.
svn path=/main/trunk/; revision=8686
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
svn path=/main/trunk/; revision=8682
|
|
|
|
|
|
|
| |
"${T}/environment" does not exist, except for "clean"
and "depend" phases.
svn path=/main/trunk/; revision=8680
|
|
|
|
| |
svn path=/main/trunk/; revision=8674
|
|
|
|
|
|
|
|
| |
save_ebuild_env() to config.environ().
* Add EMERGE_FROM to the READONLY_PORTAGE_VARS list.
svn path=/main/trunk/; revision=8670
|
|
|
|
|
|
|
| |
save_ebuild_env() in order to avoid making an assumption that
it hasn't been overridden.
svn path=/main/trunk/; revision=8663
|
|
|
|
|
|
|
| |
note the remaining assumption that save_ebuild_env() is not
overridden by the environment being loaded.
svn path=/main/trunk/; revision=8662
|
|
|
|
|
|
| |
when the ebuild function is not defined.
svn path=/main/trunk/; revision=8659
|
|
|
|
|
|
|
| |
pkg_postinst, pkg_prerm, pkg_postrm, and pkg_config functions
since they do nothing more than clutter the environment.
svn path=/main/trunk/; revision=8655
|