We need an entry in /usr/portage/profiles/use.local.desc to explain what the bindist flag actually does for this package. Reproducible: Always Steps to Reproduce: equery u mplayer (with >=app-portage/gentoolkit-0.3) Actual Results: * Found these USE flags for media-video/mplayer-1.0_rc4_p20101114: U I [...] - - bidi : Enables bidirectional language support - - bindist : Flag to enable or disable options for prebuilt (GRP) packages (eg. due to licensing issues) - - bl : Blinkenlights video output [...] Expected Results: An explanation that (apparently) one must disable bindist to allow win32codecs, amr, or faac support. A user shouldn't have to slog through an ebuild to find out what a USE flag (especially one with such a useless default description) actually does.
English is mot my native language. For me, the bindinst description is not only useless, it is simply fully non understandable. I don't even know, without to read all the ebuilds that use this flag, if USE="bindinst" will enable or disable the "options" (???) for prebuilt (GRP) packages.
This needs to be fixed. A local bindist description should be provided in order to clarify what specifically happens when USE="+bindist".
+ 08 Feb 2013; Alexis Ballier <aballier@gentoo.org> metadata.xml: + describe bindist as enforcing REQUIRED_USE, bug #369251 +
