Let's say I have two profiles: base and subprofile, with subprofile inheriting base. If base has:
and subprofile has:
Portage appends 3.3 as if PYTHON_TARGETS were incremental. However, if I do:
Invalid '-' operator in non-incremental variable 'PYTHON_TARGETS': '-*'
and ignores the unset.
Now, reading PMS. '5.3.2 Specific variables and their meanings' says:
Defines a list of variables which are to be treated incrementally
and whose contents are to be expanded into the USE variable as passed
to ebuilds. See section 11.1.1 for details.
So I'd say Portage should treat it fully incrementally, and respect '-flag' incl. '-*'. CC-ing pms-bugs@ to confirm.
I have a patch in this branch:
I'll post it for review after I've added some unit tests.
I've posted a patch with tests for review here:
This is in the master branch now:
(In reply to Zac Medico from comment #3)
> This is in the master branch now:
The above commit broke tests strangely somehow, so here it is with fixup:
Here's the final version which uses filter(None, self.make_defaults_use) to fix the previously mentioned test failure:
This is in the portage-2.2.15 release.
*** Bug 351591 has been marked as a duplicate of this bug. ***