| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
or keeptemp since these features may confuse users and lead them
to report invalid bugs.
|
|
|
|
|
| |
disable warnings about "missing repo_name entries" for the stable
branch.
|
|
|
|
|
| |
in the upcoming 2.1.9 branch which will not have sets support but will
still have the code in private and disabled form.
|
|
|
|
|
|
| |
None before trying to use them. This will be useful in the upcoming
2.1.9 branch which will not have preserve-libs support but will
still have the code in private and disabled form.
|
|
|
|
|
|
| |
trying to minimize the diff between the master branch and upcoming
2.1.9 branch which will not have preserve-libs support but will
still have the code in private and disabled form.
|
|
|
|
|
|
| |
trying to minimize the diff between the master branch and upcoming
2.1.9 branch which will not have preserve-libs support but will
still have the code in private and disabled form.
|
| |
|
|
|
|
|
| |
consumers. Once the relevant api changes are in a portage release with
stable keywords, make these warnings unconditional.
|
| |
|
|
|
|
| |
supported in python3, as reported in bug 241132, commment #4.
|
|
|
|
|
|
|
|
| |
by default in order to minimize the impact of any bugs.
* If _wrapped_select_pkg_highest_available_imp returns an installed
package when the user has not explicitly requested for this package
to be replaced (typically via an atom on the command line), reject
the installed package and try to unmask one.
|
|
|
|
| |
install actions).
|
| |
|
|
|
|
|
| |
"Performing Global Updates" routine. This option is enabled by
default.
|
|
|
|
|
|
|
| |
Expect /usr/share/portage/config/sets to be a directory containing any
number of set configuration files. The default Portage sets.conf should
be now installed as sets/portage.conf, and other ebuilds are free to
install their own set configuration files there.
|
|
|
|
| |
--depclean-lib-check=n.
|
| |
|
|
|
|
| |
invalid.
|
|
|
|
|
|
|
| |
This option makes emerge ignore binaries that would have been used
for --rebuilt-binaries, if they are older than the given timestamp.
Binaries are only reinstalled if they have a newer BUILD_TIME than
the installed package (not only unequal) with this option.
|
| |
|
|
|
|
|
|
|
| |
Instead of relying on user to provide the whole exclude list as a
space-separated list in a single argument (which is uncomfortable),
allow him/her to specify '--exclude' multiple times, joining the
provided atom lists together.
|
|
|
|
| |
unpickling.
|
|
|
|
| |
separated by whitespace.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
prior to --unmerge actions. Thanks to Thomas Sachau <tommy@gentoo.org> for the
suggestion.
svn path=/main/trunk/; revision=15486
|
|
|
|
| |
svn path=/main/trunk/; revision=15475
|
|
|
|
| |
svn path=/main/trunk/; revision=15460
|
|
|
|
| |
svn path=/main/trunk/; revision=15409
|
|
|
|
|
|
| |
enabled.
svn path=/main/trunk/; revision=15372
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
installed packages with binary packages that have been rebuilt. Rebuilds
are detected by comparison of BUILD_TIME package metadata. This option is
enabled automatically when using binary packages, so rebuilt binaries are
installed with a user's typical update command. This isn't possible with
the existing @rebuild-binaries package set since that only works with
--selective=n and therefore can't be used with a typical world update.
The package set framework should support this type of behavior sometime
in the future.
svn path=/main/trunk/; revision=15364
|
|
|
|
|
|
|
| |
that have a different build time from a currently installed package of the
exact same version.
svn path=/main/trunk/; revision=15363
|
|
|
|
|
|
| |
portage-2.1.7 when the _emerge module got split up.
svn path=/main/trunk/; revision=15322
|
|
|
|
|
|
| |
supported by stable portage.
svn path=/main/trunk/; revision=15306
|
|
|
|
|
|
| |
TERM=dumb.
svn path=/main/trunk/; revision=15191
|
|
|
|
| |
svn path=/main/trunk/; revision=15179
|
|
|
|
|
|
| |
float st_mtime in order to avoid rounding *up* in some rare cases.
svn path=/main/trunk/; revision=15125
|
|
|
|
| |
svn path=/main/trunk/; revision=15099
|
|
|
|
| |
svn path=/main/trunk/; revision=15097
|
|
|
|
|
|
|
| |
reloaded after sync, so that PORTAGE_QUIET is set when the post_sync
script is executed.
svn path=/main/trunk/; revision=14805
|
|
|
|
|
|
| |
alone, and do not display it on stdout.
svn path=/main/trunk/; revision=14783
|
|
|
|
|
|
| |
allowed, and reduce the default from 30 to 5.
svn path=/main/trunk/; revision=14763
|
|
|
|
|
|
| |
--clean is pretty useless anyway.
svn path=/main/trunk/; revision=14731
|
|
|
|
|
|
| |
the suggestion.
svn path=/main/trunk/; revision=14730
|
|
|
|
|
|
|
| |
--ask option, interpret a single "Enter" key press as invalid input. This
helps prevent accidental acceptance of the first choice.
svn path=/main/trunk/; revision=14710
|
|
|
|
|
|
|
| |
to be optimized differently since the merge order is not preserved. Thanks
to Sebastian Mingramm (few) for the initial patch.
svn path=/main/trunk/; revision=14703
|
|
|
|
|
|
| |
it like other boolean options.
svn path=/main/trunk/; revision=14667
|