Given I have the default profile of python_single_target_python3_11, if I now install a package with python_single_target_python3_10 that also depends on another package with python_single_target_python3_10, then autounmask fails, since it only unmasks python_single_target_python3_10 but does not mask python_single_target_python3_11. Example: https://dpaste.org/hRfG6 In the example I think it would be much better if the autounmask changes were >=sci-physics/lhapdf-6.5.4 python_single_target_python3_10 -python_single_target_python3_11 such that the compilation could start. However I unfortunately see two problems with adding such a feature: MAJOR) If one looks beyond the simple case of single_target_XYZ flags checking the complete REQUIRED_USE in autounmaks might not be feasible MINOR) autounmask would actually masking something Is this somehow still possible or is there some workaround to this? I am looking at this in the context of pkg-testing-tools looping over every single_target_XYZ (python or lua) and it would be super convenient if the autounmask resulted in corrected single target dependencies.
Please don't use pastebins as they expire. Please include attachments instead.
Created attachment 880262 [details] Example
We may need to do something like the REQUIRED_USE translation to implications discussed in GLEP 73: https://www.gentoo.org/glep/glep-0073.html#concept-for-transforming-required-use-into-implications
