| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
is almost certain to succeed in that case. This provides access to
the portage.exception namespace which is needed for later exception
handling, like if portage.exception.PermissionDenied is raised when
constructing the legacy global config instance.
svn path=/main/trunk/; revision=8882
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Bar-Lev <alonbl@gentoo.org> for this patch.
svn path=/main/trunk/; revision=8851
|
|
|
|
| |
svn path=/main/trunk/; revision=8839
|
|
|
|
|
|
|
| |
generation with the conditional that triggers distcc and
ccache FEATURES setup.
svn path=/main/trunk/; revision=8833
|
|
|
|
| |
svn path=/main/trunk/; revision=8824
|
|
|
|
|
|
| |
preserved libs that don't have any consumers left. Also fix the notice if preserved libs are found to use the preserved-rebuild package set instead of revdep-rebuild.
svn path=/main/trunk/; revision=8821
|
|
|
|
|
|
| |
* unset CCACHE_* and DISTCC_* variables in save_ebuild_env()
svn path=/main/trunk/; revision=8818
|
|
|
|
|
|
|
| |
save_ebuild_env() since that variable may be initialized in
global scope.
svn path=/main/trunk/; revision=8816
|
|
|
|
|
|
| |
we don't want to exit here.
svn path=/main/trunk/; revision=8808
|
|
|
|
| |
svn path=/main/trunk/; revision=8807
|
|
|
|
|
|
|
| |
if called during the "depend" phase with a flag that uses
IUSE defaults.
svn path=/main/trunk/; revision=8805
|
|
|
|
|
|
|
|
| |
* blacklist the same variables in save_ebuild_env() so that
the latest values from the calling environment always
override those from the ebuild environment
svn path=/main/trunk/; revision=8796
|
|
|
|
|
|
|
| |
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
|