| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some flags are considered to be implicit members of IUSE:
* Flags derived from ARCH
* Flags derived from USE_EXPAND_HIDDEN variables
* Forced flags, such as those from {,package}use.force
(trunk r8944)
svn path=/main/branches/2.1.2/; revision=8947
|
|
|
|
|
|
|
|
|
|
| |
possible to create awk, make, and patch symlinks that
behave analogously. These symlinks will make
it unnecessary for default-bsd profiles to define
profile.bashrc aliases for these commands.
(trunk r8941:8943)
svn path=/main/branches/2.1.2/; revision=8946
|
|
|
|
|
|
| |
leading ${D} from file paths. (trunk r8935)
svn path=/main/branches/2.1.2/; revision=8936
|
|
|
|
|
|
| |
Arahesis <arfrever.fta@gmail.com>. (trunk r8932)
svn path=/main/branches/2.1.2/; revision=8933
|
|
|
|
|
|
| |
(trunk r8927 and r8930)
svn path=/main/branches/2.1.2/; revision=8931
|
|
|
|
|
|
| |
output for display in $EDITOR. (trunk r8928)
svn path=/main/branches/2.1.2/; revision=8929
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in $EDITOR while the user creates a commit message.
Otherwise, the user would not be able to see this output
once the editor has taken over the screen.
Output is done through a formatter object where it is
captured for later use. A file-like object that behaves
something like the portage.output.colorize() function is
used to transfor style identifiers from the formatter
framework into actual console codes.
(trunk r8925)
svn path=/main/branches/2.1.2/; revision=8926
|
|
|
|
|
|
|
|
| |
take over the screen so there is an
opportunity to review any QA warnings.
(trunk r8923)
svn path=/main/branches/2.1.2/; revision=8924
|
|
|
|
|
|
|
|
|
|
|
| |
as a delimiter (Ctrl-d) instead of a new line.
* Add support for getting a commit message using an editor defined
by the EDITOR environment variable.
(trunk r8919:8921)
svn path=/main/branches/2.1.2/; revision=8922
|
|
|
|
|
|
| |
in this branch.
svn path=/main/branches/2.1.2/; revision=8919
|
|
|
|
|
|
| |
slot collisions and world file updates. (trunk r8917)
svn path=/main/branches/2.1.2/; revision=8918
|
|
|
|
|
|
|
|
|
| |
contains "strip" or "binchecks". This is needed at least for the
glibc ebuild since it calls prepallstrip directly, resulting in
it being called twice. Thanks to loki_val for reporting.
(trunk r8915)
svn path=/main/branches/2.1.2/; revision=8916
|
|
|
|
|
|
|
| |
with a reference to the CONFIGURATION FILES section of emerge(1).
(trunk r8913)
svn path=/main/branches/2.1.2/; revision=8914
|
|
|
|
|
|
| |
by "${T}"/environment. (trunk r8911)
svn path=/main/branches/2.1.2/; revision=8912
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8905
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
SLOT. (trunk r8895)
svn path=/main/branches/2.1.2/; revision=8902
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8900
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
creation appears to be missing. (trunk r8886:8888 and r8897)
svn path=/main/branches/2.1.2/; revision=8898
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
* When available, make getconfig() include an invalid token
in a ParseError message.
(trunk r8883)
svn path=/main/branches/2.1.2/; revision=8885
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
consistently nested inside <part> tags. (trunk r8877)
svn path=/main/branches/2.1.2/; revision=8880
|
|
|
|
|
|
| |
hooks that can be defined via bashrc. (trunk r8876)
svn path=/main/branches/2.1.2/; revision=8879
|
|
|
|
|
|
|
| |
where it spawns misc-functions.sh after the install phase.
(trunk r8874)
svn path=/main/branches/2.1.2/; revision=8875
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8873
|
|
|
|
|
|
|
|
| |
allowed to leak into the ebuild environment. Also, fix spawnebuild
to properly filter the env when it spawns misc-functions.sh after
the install phase. (trunk r8863:8867)
svn path=/main/branches/2.1.2/; revision=8868
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
portage.pkgmerge() and dblink.unmerge() since it's
already called in doebuild(). (trunk r8835)
svn path=/main/branches/2.1.2/; revision=8836
|
|
|
|
|
|
|
| |
generation with the conditional that triggers distcc and
ccache FEATURES setup. (trunk r8833)
svn path=/main/branches/2.1.2/; revision=8834
|
|
|
|
|
|
|
|
|
| |
critical for doebuild() operation and we already know the category.
* Always call config.setcpv() prior to config.load_infodir() so that
the CATEGORY is always known.
(trunk r8830:88310
svn path=/main/branches/2.1.2/; revision=8832
|
|
|
|
|
|
|
| |
inside PORTAGE_TMPDIR since, unlike /tmp, it can't be mounted with
the "noexec" option. (trunk r8828)
svn path=/main/branches/2.1.2/; revision=8829
|
|
|
|
|
|
| |
#201082. (trunk r8826)
svn path=/main/branches/2.1.2/; revision=8827
|
|
|
|
|
|
|
|
|
| |
because it's not needed and the ebuild path that's passed in for
postinst is may be from the portage tree, which causes load_infodir()
to discard critical metadata such as CATEGORY without realoading
it. (trunk r8822)
svn path=/main/branches/2.1.2/; revision=8823
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
|
|
|
| |
already-installed instance" logic to make sure that
it works in all possible cases. (trunk r8801)
svn path=/main/branches/2.1.2/; revision=8802
|
|
|
|
| |
svn path=/main/branches/2.1.2/; revision=8800
|