The ALSA_PCM_PLUGINS variables should be easier to find (other than looking in the actual ebuild). One suggestion is to display them in pkg_setup's warning message such as: ... ewarn "Plugins are set with ALSA_PCM_PLUGINS=\"...\" in make.conf" ewarn "Valid plugins are ${IUSE_PCM_PLUGIN}" The same should be done if the USE flag approach is preferred (display the alsa_pcm_plugins_* variant). Reproducible: Always Steps to Reproduce: Note that the make.conf manpage doesn't mention this variable, nor does the official alsa guide (http://www.gentoo.org/doc/en/alsa-guide.xml). Since these flags were created for a specific subset of users, it would be strongly recommended (imho) that the default behavior be the opposite, ie: if no flag is set, build _all_ PCM modules.
Seems your suggestion was followed. I have not set ALSA_PCM_PLUGINS but _a_lot_ of flags are set doing an emerge -p alsa-lib. I'm using the default/linux/amd64/2008.0/desktop profile.
> Since these flags were created for a specific subset of users, it would be > strongly recommended (imho) that the default behavior be the opposite, ie: if > no flag is set, build _all_ PCM modules. That's actually the case now, and has been for a while I think ... closing bug. :)
