This feature is NOT meant for hiding those scanelf QA warnings; that's what QA_{TEXTRELS,EXECSTACK,WX_LOAD} is for when the package can't be fixed. RESTRICT="binchecks" should _only_ be used for stuff where these checks don't make any sense and just cause needless overhead (pure data stuff, like kernel sources, icon packs, themes, fonts etc.)
QA: Removed invalid use of RESTRICT=binchecks
Why do you just remove the RESTRICT-statement without a proper fix? (actually breaking the ebuild for everyone who uses FEATURES="stricter" if I remember right) For openoffice-bin we use the upstream binary, the checks report a few hundred hits, should I now add all these to the ebuild?
Errr, it's not any more or less broken than it was with the bad restrict. (And, mind you that FEATURES=stricter is not intended for users in general, it's a developer feature). Anyway, RESTRICT=binchecks is NOT aimed at hiding this stuff, it's a feature to disable redundant checks for stuff where it doesn't make sense. zmedico already clarifies ebuild(5) manpages in this respect. What you probably intended was RESTRICT="stricter", then move to Bug 131633. RESTRICT=binchecks should not be used for stuff that installs ELF binaries, end of story.
To quote ebuild(5) in sys-apps/portage-2.1.2_rc2-r5: binchecks Disable all QA checks for binaries. This should ONLY be used in packages for which binary checks make no sense (linux-headers and kernel-sources, for example, can safely be skipped since they have no binaries). If the binary checks need to be skipped for other reasons (such as proprietary binaries), see the QA CONTROL VARIABLES section for more specific exemptions. If you think that RESTRICT="stricter" should exist, then there's Bug 131633. Closing this again.
