Summary: | Autounmask disables use flag for lone explicit package | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Nikita Zlobin <cook60020tmp> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nikita Zlobin
2021-04-21 14:22:41 UTC
*** Bug 787929 has been marked as a duplicate of this bug. *** Found solution, for now for unconditional use dependencies. I utterly missed some changes in portage/emerge configuration: 1. autounmask features disappeared from FEATURES in make.conf, now they are only in emerge options. However, '--autounmask-use y' is still not enough. 2. I just discovered in emerge manual: If --binpkg-respect-use is given explicitly, then it implies --autounmask-use=n, because these options naturally oppose eachother. After I added '--binpkg-respect-use n' to emerge arguments, use autounmask started to work (at the time of discovery, it was unconditional use dependency). Conditional use dependencies still exhibit described counterproductive behavior, example with wine-vanilla (wants -abi_x86_32 since some use dependencies for this flag are not satisfied). Err, this time I stupidly forgot to add '--binpkg-respect-use n'. In short - it works. I assume it's fine if I just close this bug, since noone ever reacted to it. (perhaps they have no time for such nonsense). |