Hi, It seems to be a pattern now to mask the language "target" USE flags for unstable versions, such as python_targets_python3_3 and php_targets_php5-5.
This is very handy since e.g I do not need two revisions of dev-php/xdebug: - one that can be stabilised, supporting stable php5.3 and php5.4and one supporting - one that cannot be stabilised supporting also php5.5 However, now the time has come for php5.5 to be stabilised, and all is working great except that I cannot remove php_targets_php5-5 from use.stable.mask until all arches have stabilised php. For those arches with stable php5.5, confusion arise when they see that they cannot enable php5.5 for any ebuilds without first adding them to ~arch. This have led to bug 481532 as well as comments in stabilisation req bug 480460 A part of the problem is that x86 and amd64 is stabilised fairly quickly after filing the stabilisation bug, while for the other arches it often takes some more time. I suppose the problem could have been mitigated by each arch team stating it can be stabilised in the bug, and then do the actual keywordking at the same time. Does anyone have any idea how to handle this issue? -- Ole Markus
