We need an entry in /usr/portage/profiles/use.local.desc to explain what the bindist flag actually does for =www-plugins/adobe-flash-10.2.159.1_p201011173. Reproducible: Always Steps to Reproduce: equery u =www-plugins/adobe-flash-10.2.159.1_p201011173 (with >=app-portage/gentoolkit-0.3) Actual Results: * Found these USE flags for www-plugins/adobe-flash-10.2.159.1_p201011173: U I [...] - - bindist : Flag to enable or disable options for prebuilt (GRP) packages (eg. due to licensing issues) [...] Expected Results: An explanation that (apparently) one must disable bindist to get the fix for bug #354073. Since this appears to be a temporary fix only used in one ebuild, please keep this in mind for any uses of bindist by this package in the future. 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) does for a particular package.
I understand your frustration, as I also get tired of reading ebuilds to figure out what they're for. And I've taken your point and added a local description regarding this specific flag: ---- With USE="-bindist", applies a binary patch to the native 64-bit plugin for compatibility with glibc-2.13 (Bug #354073). Required due to the non-modification clause in Adobe's license. ---- Thanks for the report!
