gentoo/cvs/gentoo-x86/kde-base/kdesdk $ grep valgrind kdesdk-* kdesdk-3.5.5.ebuild:DEPEND="x86? ( >=dev-util/valgrind-3.2.0 ) kdesdk-3.5.6.ebuild:DEPEND="x86? ( >=dev-util/valgrind-3.2.0 ) kdesdk-3.5.6-r1.ebuild:DEPEND="!alpha? ( !sparc? ( !ia64? ( >=dev-util/valgrind-3.2.0 ) ) ) kdesdk-3.5.7.ebuild:DEPEND="!alpha? ( !sparc? ( !ia64? ( >=dev-util/valgrind-3.2.0 ) ) ) kdesdk-3.5.8.ebuild:DEPEND="!alpha? ( !sparc? ( !ia64? ( >=dev-util/valgrind-3.2.0 ) ) ) 1) Rather than adding arch after arch that valgrind has no use for, it would be better to simply add a USE=valgrind, use.mask that generally and reenable it specifically for x86. 2) If that's too much trouble, then maybe it's better to not pull in valgrind at all, in exactly the same way that kdesdk-4 doesn't, and maybe add an einfo to the effect that installing valgrind might help using kdesdk. I suggest this because the ebuilds and eclasses in no way use valgrind, which in turn suggests that the build system automagically depends on valgrind or that valgrind is merely a runtime dependency and should be in RDEPEND, not DEPEND.
This is basically a dupe of Bug 158066 for kde-base/kcachegrind; I reopened it now. I don't get this either.
Created attachment 143219 [details, diff] =kdesdk-207937-valgrind-removal.patch
Thanks. The dependency is going away. It isn't needed at all at run or build time. *** This bug has been marked as a duplicate of bug 158066 ***
