Currently, it is only possible to mask bindist restricted ebuilds completely, by setting -bindist in ACCEPT_RESTRICT or --accept-restrict. It would be nice if there was an option and/or variable that would suppress only building of binary packages for bindist restricted ebuilds, but otherwise not influence installation.
We could always introduce RESTRICT=binpkg , which, if used in an ebuild, forbids the generation of a binary package.
(In reply to Andreas K. Hüttel from comment #1) > We could always introduce RESTRICT=binpkg , which, if used in an ebuild, > forbids the generation of a binary package. Sorry, but I see little use for such a restriction at the ebuild level. How would it be differenciated against "bindist" restriction, which exists mostly for license reasons? Whether binpkgs should be built for bindist-restricted ebuilds seems to fit better with user preferences like FEATURES or an emerge options.