| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
dump the current environment to ${T}/die.env in case it helps
for debugging.
svn path=/main/trunk/; revision=8783
|
|
|
|
|
|
| |
* filter PREROOTPATH in save_ebuild_env()
svn path=/main/trunk/; revision=8781
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
variable and we don't want to interfere.
svn path=/main/trunk/; revision=8770
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
in the stack trace and the user is likely to be interested in it.
svn path=/main/trunk/; revision=8678
|
|
|
|
| |
svn path=/main/trunk/; revision=8676
|
|
|
|
| |
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
|
|
|
|
| |
svn path=/main/trunk/; revision=8666
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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.
svn path=/main/trunk/; revision=8654
|
|
|
|
|
|
|
| |
that the user will not be interested in. Therefore, the stack trace
should only show calls that come after qa_call().
svn path=/main/trunk/; revision=8653
|
|
|
|
|
|
| |
* Run the "clean" phase if pkg_config() succeeds.
svn path=/main/trunk/; revision=8651
|
|
|
|
|
|
|
|
|
|
|
| |
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.
svn path=/main/trunk/; revision=8649
|
|
|
|
|
|
| |
function doesn't exist.
svn path=/main/trunk/; revision=8647
|
|
|
|
|
|
| |
virtuals since they don't directly install anything.
svn path=/main/trunk/; revision=8645
|
|
|
|
| |
svn path=/main/trunk/; revision=8643
|
|
|
|
| |
svn path=/main/trunk/; revision=8640
|
|
|
|
|
|
|
|
| |
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.
svn path=/main/trunk/; revision=8636
|
|
|
|
|
|
| |
it's properly local.
svn path=/main/trunk/; revision=8634
|
|
|
|
|
|
| |
condense redundant identical expressions into a single one.
svn path=/main/trunk/; revision=8630
|
|
|
|
| |
svn path=/main/trunk/; revision=8629
|
|
|
|
|
|
|
|
| |
SANDBOX_{DENY,READ,PREDICT,WRITE} variables between
phases so things like the global scope addpredict()
call in qt3.eclass will continue to work.
svn path=/main/trunk/; revision=8628
|
|
|
|
|
|
| |
from the environment.
svn path=/main/trunk/; revision=8623
|
|
|
|
|
|
|
| |
behavior. The bashrcs get an opportunity to set aliases that
will be expanded during sourcing of ebuilds and eclasses.
svn path=/main/trunk/; revision=8621
|
|
|
|
| |
svn path=/main/trunk/; revision=8619
|
|
|
|
|
|
| |
after the ebuild environment is fully loaded.
svn path=/main/trunk/; revision=8617
|
|
|
|
|
|
| |
for md5sum output.
svn path=/main/trunk/; revision=8613
|
|
|
|
|
|
| |
'^declare -r ' by simply removing it.
svn path=/main/trunk/; revision=8611
|
|
|
|
|
|
| |
directing them to /dev/null.
svn path=/main/trunk/; revision=8607
|
|
|
|
|
|
| |
it will work with things like 'declare -xr' as well as 'declare -rx'.
svn path=/main/trunk/; revision=8605
|