Summary: | Keyword for saying: Merge keyworded package only if no stable version is available | ||
---|---|---|---|
Product: | Portage Development | Reporter: | gerion <gerion.entrup> |
Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
gerion
2017-01-23 17:10:00 UTC
It might be annoying if a lower version than the one install gets stabilized, especially if there's an ABI change. This is possible. Does Portage in this case force rebuilds of the affected packages? If so, the user can decide to choose the stable version (and reinstall some packages) or keep or update to a newer keyworded version. Another possibility would be to emerge the lowest keyworded version, because this is either the one, that is stabilized or it would be a regular update (and not downgrade) to the stabilized version. By the way, my current solution is to lock the version and check the log of eclean, that says if there are any ebuilds installed that are not in the tree anymore and update manually, but this is time consuming. |