On 2/23/2011 10:57 AM, Dale wrote: > Neil Bothwick wrote: >> This isn't much help, you need the parts where the KDE/QT packages are >> shown as ebuild, not nomerge. That will show you what is requiring them. >> >> emerge -ept | grep -B 4 kdelibs should find that for you, or >> >> emerge -ept | most (or your preferred pager) >> >> then search for kdelibs. >> >> > > Attached is the whole thing. I'm not sure the other would have helped > much and it was pretty long too. > > I do have a LOT of USE flags. I inspect them when I run emerge and they > have accumulated over the years. Some of them may not be valid anymore. > I need to clean them out I guess but portage is not complaining any. ;-)
Near as I can tell, your problem originates here: [nomerge ] kde-base/khelpcenter-4.6.0 [nomerge ] kde-base/kdelibs-4.6.0-r1 [ebuild R ~] kde-base/nepomuk-4.6.0 [ebuild R ~] kde-misc/polkit-kde-kcmodules-0.98_pre20101127 [ebuild R ~] kde-base/khelpcenter-4.6.0 [ebuild R ~] sys-auth/polkit-kde-agent-0.99.0 [ebuild R ~] kde-base/kdelibs-4.6.0-r1 Every other KDE or Qt package in the emerge output can be traced back to being a dependency of khelpcenter (directly or indirectly). Although technically that's not even true, since khelpcenter *doesn't* depend on kdelibs, not since 4.4.5, but your portage seems to think it still does. And once you've pulled in kdelibs, you eventually depend on everything else in the universe as well (including, of course, khelpcenter!). Do you, by any chance, have a file named /etc/portage/profile/packages? The only way for a package to get into your system set is if it's package atom is: * Listed in a file named 'packages' somewhere in your set of profile paths, and * Prefixed with a "*" within that file --Mike
