Summary: | Possibility to exclude packages from a list of pkgs to be processed | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Nico Mahlo <nico-mahlo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | blubb, nt, wakko |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nico Mahlo
2006-01-13 06:03:04 UTC
emerge pkgA pkgB pkgC pkgD --start-with pkgD pkgD depends on pkgC depends on pkgB depends on pkgA. What do we do in this case, and how do we validate the dependency graph that you just cut in half with your --start-with <package>, in a general case. Another thing that the new resolver may be able to do, definately not soon though. > emerge pkgA pkgB pkgC pkgD --start-with pkgD
> pkgD depends on pkgC depends on pkgB depends on pkgA.
> What do we do in this case[...]
In this case "emerge pkgA pkgB pkgC pkgD" would emerge the packages in the following order:
pkgA
pkgB
pkgC
pkgD
so an "emerge pkgA pkgB pkgC pkgD --start-with pkgD" would start with:
pkgA
pkgB
pkgC
pkgD <---
Means: It just emerges pkgD, assuming A,B,C are already successfully merged and that's it. :)
HTH
*** Bug 110308 has been marked as a duplicate of this bug. *** *** Bug 134500 has been marked as a duplicate of this bug. *** Let's generalize a bit: I think what you really want is a more convenient way to exclude some packages from a list of packages to be acted upon in general, not just --start-from. So what we're really after is a more powerful selecting mechanism. --ask seems to be the right place for this, a bit more interactivity then just yes/no wouldn't hurt it IMO. |