| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
See bug 379333.
|
| |
|
|
|
|
|
|
| |
Disables creation of p.unmask entries to allow users
to insist on their masks and hope for another conflict
resolution (i.e. missed update). This fixes bug 372485.
|
|
|
|
|
|
|
|
| |
The default behavior of --autounmask is now changed back to
the original one, namely to use '=' operators. The
--autounmask-unrestricted-atoms option allows the use of '>='
operators whenever possible. This addresses the issues raised
in bugs 372405, 374331 and 379333.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Right now, the --rebuild-if-* flags only rebuild packages that are used at
both run-time and build-time. This doesn't help for packages that are used
only at build-time (for example, static libaries).
Rebuilding packages whenever a build-time dependency is changed is easier to
understand and explain, and it handles all cases correctly.
BUG=chromium-os:15517
TEST=Run emerge test suite.
Change-Id: Iae8dab24e8acb6625bc1a0ce41862e90b232eb84
|
|
|
|
|
|
| |
This removes a very subtle difference in --noreplace package selection
logic which is not very useful and triggers strange package selection
choices in some cases, as reported in bug #375571.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Enabling this option together with --autounmask writes proposed
changes to config files, honoring CONFIG_PROTECT.
|
|
|
|
|
|
| |
This will fix bug #286714. The emerge --depclean-lib-check option will
now be ignored when FEATURES=preserve-libs is enabled, since any
libraries that have consumers will simply be preserved.
|
|
|
|
|
| |
If you want the graph as complete as possible, now you'll have to use
--with-bdeps=y together with --complete-graph.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replace --rebuild option with --rebuild-if-* options.
--rebuild-if-new-rev [ y | n ]
Rebuild packages when dependencies that are used at both build-time and
run-time are built, if the dependency is not already installed with the
same version and revision.
--rebuild-if-new-ver [ y | n ]
Rebuild packages when dependencies that are used at both build-time and
run-time are built, if the dependency is not already installed with the
same version. Revision numbers are ignored.
--rebuild-if-unbuilt [ y | n ]
Rebuild packages when dependencies that are used at both build-time and
run-time are built.
Change-Id: Ia50c1702bfe1b98a8d1891740e7bbb045921a905
Review URL: http://gerrit.chromium.org/gerrit/280
|
|
|
|
|
|
|
|
|
| |
A space separated list of package names or slot atoms. Emerge will not rebuild
packages that depend on matching packages due to \fB\-\-rebuild\fR.
Change-Id: Ia58fe632ed06c97a22413da0341d7f8da2d65ba8
Review URL: http://gerrit.chromium.org/gerrit/209
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rebuild when build-time/run-time deps are upgraded.
If pkgA has been updated, and pkgB depends on pkgA at both
build-time and run-time, pkgB needs to be rebuilt. This
feature ensures that all packages are consistent when
dependencies that are used at both runtime and build time
are changed.
This feature only rebuilds packages one layer deep. That
means that if you upgrade libcros, for example, packages
that depend directly on libcros will be rebuilt and
reinstalled, but indirect dependencies will not be rebuilt.
BUG=chromium-os:14296
TEST=Test whether packages rebuilding a bunch of packages.
Change-Id: Idbc0532b4b1de28fd9e5a0abe3b7dbe1a3abd2c8
Review URL: http://codereview.chromium.org/6905107
|
|
|
|
| |
This will fix bug #363137.
|
| |
|
| |
|
|
|
|
|
|
| |
This allows --ask to be enabled via EMERGE_DEFAULT_OPTS, and then
temporarily disabled via the command-line. This may be useful for
programs that call emerge non-interactively, as in bug #360233.
|
|
|
|
|
|
| |
This allows --quiet and --quiet-build to be enabled via
EMERGE_DEFAULT_OPTS, and then temporarily disabled via the command-
line.
|
| |
|
| |
|
|
|
|
| |
This will fix bug #354437.
|
|
|
|
| |
This will fix bug #346349 and bug #344799.
|
|
|
|
|
|
|
|
| |
The bug was solved in principle, but other conflicts could
lead to all tries being used up too early.
The default backtrack limit is changed from 5 to 10.
The maximal depth of the backtrack graph is now half of the
backtrack limit.
|
| |
|
|
|
|
| |
masks.
|
| |
|
|
|
|
| |
is False.
|
|
|
|
| |
and warnings advising use of revdep-rebuild.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
should remain enabled under normal circumstances.
|
|
|
|
|
| |
"Performing Global Updates" routine. This option is enabled by
default.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
separated by whitespace.
|
| |
|
| |
|
|
|
|
|
|
| |
for wording suggestions.
svn path=/main/trunk/; revision=15831
|
|
|
|
| |
svn path=/main/trunk/; revision=15777
|
|
|
|
| |
svn path=/main/trunk/; revision=15776
|
|
|
|
|
|
|
| |
prior to --unmerge actions. Thanks to Thomas Sachau <tommy@gentoo.org> for the
suggestion.
svn path=/main/trunk/; revision=15486
|
|
|
|
|
|
|
|
| |
--getbinpkgonly mode, since --usepkgonly behaves better in cases when
the portage tree is not exactly the same revision that was used to
build the packages.
svn path=/main/trunk/; revision=15427
|
|
|
|
|
|
| |
enabled.
svn path=/main/trunk/; revision=15372
|
|
|
|
| |
svn path=/main/trunk/; revision=15367
|