When running updates on a system that contains a package now calling for dev-lang/perl[perl_features_ithreads] in response to the USE flag change from bug 930123, the automated response from portage is to add this USE flag to package.use This is WRONG, both with respect to automation scripts that are not programmed to write changes directly to make.conf AND to unexpecting users not interpreting the underscores in the USE flag name as a global USE flag requirement rather than a package USE flag requirement that is in fact supposed to be broken up as PERL_FEATURES=ithreads Portage should not offer to write USE flag changes to package.use when they contain underscores. If this mechanism is still to be maintained then portage should write */* perl_features_ithreads to package.use so that it applies globally rather than on the single package. In case of portage being run interactively, portage should also not print that it wants to set USE=perl_features_ithreads but display the requirement in the proper intended form, i.e. PERL_FEATURES=ithreads
*** This bug has been marked as a duplicate of bug 930123 ***
Not a duplicate - caused by
You have filed this bug with a nonsense summary, in the wrong product/component, and with a description that is difficult to understand. I am therefore closing it as invalid. Please take some time to collect yourself and create a new bug with a better description once your thoughts are more organized.
So under what category should I file a bug where emerge --automask sets and unsets the same USE flag on every individual run?
That would likely fit into the "Portage Development" product.
