Probably dev-util/perf ebuild should resolve distribution file name to .xz archive, as it does by every kernel ebuild, instead of .bz2. So, giving you have installed sys-kernel/gentoo-sources 3.12 and 3.13, you have in a distfiles: $ ls -l /usr/portage/distfiles/linux-* -rw-rw-r-- 1 portage portage 76384600 Nov 4 01:47 /usr/portage/distfiles/linux-3.12.tar.xz -rw-rw-r-- 1 portage portage 77187032 Jan 20 04:59 /usr/portage/distfiles/linux-3.13.tar.xz after installing dev-util/perf I got one more tarball: $ ls -l /usr/portage/distfiles/linux-* -rw-rw-r-- 1 portage portage 91111381 Nov 4 01:47 /usr/portage/distfiles/linux-3.12.tar.bz2 -rw-rw-r-- 1 portage portage 76384600 Nov 4 01:47 /usr/portage/distfiles/linux-3.12.tar.xz -rw-rw-r-- 1 portage portage 77187032 Jan 20 04:59 /usr/portage/distfiles/linux-3.13.tar.xz
And is it possible to make dev-util/perf sloted? And do some wrapper to automatic choose version depending on running kernel?
(In reply to Denis Sokolovsky from comment #1) perf should be backwards compatible so there should be no need for slots. if it does break, then you should report the issue upstream so they can fix it.
perf-3.13.1 now uses tar.xz in SRC_URI