Many gnome packages currently preset USE flags like socialweb, cups, cheese,networkmanager indepently to 'active' (using +<useflag>) Reproducible: Always Steps to Reproduce: N/A Actual Results: N/A Expected Results: N/A Most of these enforced USE flags are features that in no way make up a desktop and as such should be excluded except if the user wishes to USE them. They should be preset as inactive in component packages and their preset should be handled in either gnome's metapackage or in the profile's USE flags preset.
(In reply to comment #0) > Most of these enforced USE flags are features that in no way make up a desktop > and as such should be excluded except if the user wishes to USE them. I am afraid I must disagree. We (the gnome team) aim for a *reasonable experience by default*. In other words, if most users of package x will probably want to emerge it with USE=y, then we put "+y" in x's IUSE. We want to decrease the number of lines in /etc/portage files that the average user would need to edit. Here are specific considerations I look for when considering USE flag defaults: * are there other packages that depends on this one that require this feature to be enabled or disabled? * does this feature require heavy dependencies that take a long time to compile? * will the majority of users of this package want this feature? * will the majority of users of this package already have all prerequisites for this feature installed? * what are the disadvantages of this feature? Would enabling it lead to a worse experience for a sizable category of users? * might this package be installed by someone who is not using the desktop/gnome portage profile? Would such a user's expectations differ from those of a gnome user? Of course it is entirely possible that in some cases we made bad judgments about the defaults. However, we need you to provide concrete issues (e.g. "package X should not have USE flag Y enabled by default because a, b, c"), not a general statement that we enabled too many flags :)
I second all of what Alexandre said.
This is likely wontfix as explained
