| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
save_ebuild_env() in order to avoid making an assumption that
it hasn't been overridden. (trunk r8663)
svn path=/main/branches/2.1.2/; revision=8665
|
|
|
|
|
|
|
| |
note the remaining assumption that save_ebuild_env() is not
overridden by the environment being loaded. (trunk r8662)
svn path=/main/branches/2.1.2/; revision=8664
|
|
|
|
|
|
| |
when the ebuild function is not defined. (trunk r8659)
svn path=/main/branches/2.1.2/; revision=8660
|
|
|
|
|
|
|
|
| |
pkg_postinst, pkg_prerm, pkg_postrm, and pkg_config functions
since they do nothing more than clutter the environment.
(trunk r8655)
svn path=/main/branches/2.1.2/; revision=8658
|
|
|
|
|
|
|
|
|
| |
will be useful if an environment.bz2 has been loaded and it has
missing functions for some reason. For example, there are a lot
of default functions that are empty and could simply be omitted
from the environment. (trunk r8654)
svn path=/main/branches/2.1.2/; revision=8657
|
|
|
|
|
|
|
| |
* Run the "clean" phase if pkg_config() succeeds.
(trunk r8651)
svn path=/main/branches/2.1.2/; revision=8652
|
|
|
|
|
|
|
|
|
|
|
| |
Since a temporary directory is required for processing of
${T}/environment, and we want a user who's not in the portage
group to be able to run the pkg_info() phase, PORTAGE_TMPDIR
is temporarily overridden with a directory created by mkdtemp.
To make this work, doebuild() creates the tempdir and cleans
it up in a finally block. (trunk r8649)
svn path=/main/branches/2.1.2/; revision=8650
|
|
|
|
|
|
| |
function doesn't exist. (trunk r8647)
svn path=/main/branches/2.1.2/; revision=8648
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8641
|
|
|
|
|
|
|
|
|
| |
environment in order to avoid potential interference problems.
For example, having an invalid value for SANDBOX_LOG prevents
the sandbox from killing the ebuild when a violation occurs.
(trunk r8636)
svn path=/main/branches/2.1.2/; revision=8637
|
|
|
|
|
|
| |
it's properly local. (trunk r8634)
svn path=/main/branches/2.1.2/; revision=8635
|
|
|
|
|
|
| |
condense redundant identical expressions into a single one. (trunk r8630)
svn path=/main/branches/2.1.2/; revision=8633
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8632
|
|
|
|
|
|
|
|
|
| |
SANDBOX_{DENY,READ,PREDICT,WRITE} variables between
phases so things like the global scope addpredict()
call in qt3.eclass will continue to work.
(trunk r8628)
svn path=/main/branches/2.1.2/; revision=8631
|
|
|
|
|
|
| |
from the environment. (trunk r8623)
svn path=/main/branches/2.1.2/; revision=8624
|
|
|
|
|
|
|
|
| |
behavior. The bashrcs get an opportunity to set aliases that
will be expanded during sourcing of ebuilds and eclasses.
(trunk r8621)
svn path=/main/branches/2.1.2/; revision=8622
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8620
|
|
|
|
|
|
| |
after the ebuild environment is fully loaded. (trunk r8617)
svn path=/main/branches/2.1.2/; revision=8618
|
|
|
|
|
|
| |
'^declare -r ' by simply removing it. (trunk r8611)
svn path=/main/branches/2.1.2/; revision=8612
|
|
|
|
|
|
| |
directing them to /dev/null. (trunk r8607)
svn path=/main/branches/2.1.2/; revision=8608
|