Installing binary blob games on amd64 which are 32bit only, I will get something like this: >>> /usr/lib/debug/opt/dynamitejack/bin/main.debug >>> /usr/lib/debug/.build-id/73/bd4ebb4ef3e51e0faae2edb87d1ef90c40642e.debug -> ../../opt/dynamitejack/bin/main.debug >>> /usr/lib/debug/.build-id/73/bd4ebb4ef3e51e0faae2edb87d1ef90c40642e -> /opt/dynamitejack/bin/main affected packages which I force to error out on FEATURES="splitdebug" in pkg_pretend for now: games-action/beathazardultra games-action/solar2 games-action/swordandsworcery games-action/trine2 games-arcade/dynamitejack games-rpg/bastion games-rpg/grimrock Those are all games that install bundled 32bit libraries and binaries on amd64. Not all files are prestripped, so I see no reason to set RESTRICT="strip". Regular strip works fine.
Can you clarify what is "broken" about the current behavior? FEATURES=splitdebug is supposed to trigger creation *.debug files in /usr/lib/debug, and build-id symlinks in /usr/lib/debug/.build-id, and at first glance it seems to be working as designed. So, what's "broken" about it?
I guess you're confused since you don't have LDFLAGS="-Wl,--build-id" locally, so you're not accustomed to those build-id symlinks.
Support RESTRICT=splitdebug: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=11273a03c21fac1f2af89d89d6f2c1b9ba480043