On 12/28/2015 10:24 AM, [email protected] wrote: > I’m suffering from the fact that users can distinguish packages containing > binaries just by eye. There is no mechanism to allow/ignore such packages. > For license restrictions we have ‘package.license/’ whitelist.
We can use the PROPERTIES variable (or alternatively the RESTRICT variable) to tag this information in the ebuild. Portage has a ACCEPT_PROPERTIES configuration variable, and a package.properties file that can be used to mask and unmask packages based on PROPERTIES. It would be useful to be able to do this with "live" ebuilds too... -- Thanks, Zac
