Summary: | sys-apps/portage: score binary packages by difference between built USE configuration and desired USE configuration as alternative to --binpkg-respect-use | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra, gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=772380 https://bugs.gentoo.org/show_bug.cgi?id=780390 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155723 |
Description
Zac Medico
2021-03-18 20:18:38 UTC
If this were implemented, there should be a way of specifying the "importance" of a USE flag so that an important difference isn't overlooked for a minor one. For example in sys-apps/glibc, USE=headers-only has a much greater impact on the resulting package than the doc flag. Another point would be having ABI-changing flags have a very high score. Unfortunately, my suggestion here may require a future EAPI change or an additional attribute in the <use> element in metadata.xml since it is not feasible to hard-code that kind of information into portage itself. We can allow users to side-load ranks so that they can be used without any EAPI support. (In reply to Emily Rowlands from comment #1) > If this were implemented, there should be a way of specifying the > "importance" of a USE flag so that an important difference isn't overlooked > for a minor one. I suppose we should also allow this rank to have different values per package/USE flag combination. |