Summary: | sys-apps/portage: autounmask should (add an option to) prefer unmasking lowest, rather than highest, version satisfying dependencies | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jonathan Lovelace <kingjon3377> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 376695 |
Description
Jonathan Lovelace
2015-08-03 18:35:05 UTC
Short answer, no. Longer answer, Portage is already getting too many cli options. Also portage has always choosen the highest available version number. Adding in even more logic to an already overloaded and slow dependency resolver is not going to happen. There is too much AI (artificial intelegence) needed to figure out if it should be the lowest masked or highest... depends on the problem and which it was fixed in, which of the ~arch keyworded pkgs are going to be stabilized by the maintainer next,... That is what the system maintainer is to decide. Mask or unmask the pkg-version desired if you don't like the choice made by autounmask. That's why it give you the choice to accept it of reject it's choice. |