KCachegrind 0.4.5kde is part of KDE 3.3 (package kdesdk), so there is no need to install the kcachegrind 0.4.5 ebuild on a system using KDE 3.3 or it would result in kcachegrind being present TWO times on the system. The ebuild should take care that no double-install is made Reproducible: Always Steps to Reproduce: 1. emerge =kdesdk-3.3 2. emerge =kcachegrind-0.4.5 3.kcachegrind binaries installed TWO times on the system
Don't they already block each other?
Gregorio is right. If you use a Portage .51-preXX version, then you may have detected a problem with blockers, otherwise it's a local problem - Portage cannot care about anything you may have installed by hand beside emerge <foo>. Please reopen if it's not a local problem.