Summary: | sync ebuilds of installed packages only | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Tim Cera <tim> |
Component: | Conceptual/Abstract Ideas | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | frustrated, gavin, jieryn, rockoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Diff of patched emerge to only sync ebuilds of installed packages |
Description
Tim Cera
2004-03-12 19:22:11 UTC
Created attachment 27271 [details, diff]
Diff of patched emerge to only sync ebuilds of installed packages
Diff against emerge CVS version 1.264, portage-2.0.50-r1, on 3/12/2004.
What about changing dependencies? If you alter your use flags you may pull in a new dependency... which will probably break after a short while with this method. The only "perfect" way to resolve this issue would be a complete dep resolver and get each package. The idea is good, but there are side effect to it. Minimally it needs a warning that it isn't always going to work as expected. Nicholas, thanks for your comments. My patch is not even close to a complete solution and you are correct that there is a problem if the dependencies change. A finished implementation would catch changed dependencies and add the new ebuild(s) to the sync list and sync the new ebuild. Foreward duping this on 45221, since the concept there is a bit saner (this approach would require multiple rounds of sync's to get all deps. This would suck.) *** This bug has been marked as a duplicate of 45221 *** *** Bug 58571 has been marked as a duplicate of this bug. *** |