| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
code can assume there are no blockers. (trunk r8889)
svn path=/main/branches/2.1.2/; revision=8890
|
|
|
|
|
|
|
|
|
| |
constructor, raise a ParseError and make emerge and portageq handle
the error. This way consumers of the portage api can handle the
ParseError rather than have their application exit. Thanks to lxnay
for reporting. (trunk r8884)
svn path=/main/branches/2.1.2/; revision=8886
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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=8873
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
period, don't show ? if the installed package
is missing a repository label. Stages starting
with 2007.1 will come with repository lables.
svn path=/main/branches/2.1.2/; revision=8855
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
repository label. The stable version of portage
creates these labels now, so false positives
won't be as common as they used to be. (trunk
r8846)
svn path=/main/branches/2.1.2/; revision=8847
|
|
|
|
|
|
|
| |
generation with the conditional that triggers distcc and
ccache FEATURES setup. (trunk r8833)
svn path=/main/branches/2.1.2/; revision=8834
|
|
|
|
|
|
|
| |
* unset CCACHE_* and DISTCC_* variables in save_ebuild_env()
(trunk r8818)
svn path=/main/branches/2.1.2/; revision=8819
|
|
|
|
|
|
|
| |
save_ebuild_env() since that variable may be initialized in
global scope. (trunk r8816)
svn path=/main/branches/2.1.2/; revision=8817
|
|
|
|
|
|
|
| |
if called during the "depend" phase with a flag that uses
IUSE defaults. (trunk r8805)
svn path=/main/branches/2.1.2/; revision=8806
|
|
|
|
|
|
|
| |
restart itself when dblink.merge() creates temporary copies of
PORTAGE_{BIN,PYM}_PATH. (trunk r8803)
svn path=/main/branches/2.1.2/; revision=8804
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8800
|
|
|
|
|
|
|
|
|
| |
* blacklist the same variables in save_ebuild_env() so that
the latest values from the calling environment always
override those from the ebuild environment
(trunk r8796)
svn path=/main/branches/2.1.2/; revision=8797
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8795
|
|
|
|
|
|
|
| |
in order to clean up zombies (such as the parallel-fetch
process). (trunk r8790:8792)
svn path=/main/branches/2.1.2/; revision=8793
|
|
|
|
|
|
|
| |
dump the current environment to ${T}/die.env in case it helps
for debugging. (trunk r8783)
svn path=/main/branches/2.1.2/; revision=8784
|
|
|
|
|
|
|
| |
* filter PREROOTPATH in save_ebuild_env()
(trunk r8781)
svn path=/main/branches/2.1.2/; revision=8782
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
variable and we don't want to interfere. (trunk r8770)
svn path=/main/branches/2.1.2/; revision=8772
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
paths that aren't writable by the current user. This prevents
Permission denied errors from being triggered later when trying
to scan subdirectories that are inaccessible. (trunk r8726)
svn path=/main/branches/2.1.2/; revision=8727
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
it cancels all binary package options.
svn path=/main/branches/2.1.2/; revision=8685
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
in the stack trace and the user is likely to be interested in it.
(trunk r8678)
svn path=/main/branches/2.1.2/; revision=8679
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8677
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
or more eclasses override eclasses from PORTDIR. The warning can be
permanently disabled by setting PORTAGE_ECLASS_WARNING_ENABLE="0" in
/etc/make.conf. (trunk r8668)
svn path=/main/branches/2.1.2/; revision=8669
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8667
|
|
|
|
|
|
|
| |
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
|