Mike Edenfield wrote:
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
I don't even have the profile directory:
root@fireball / # ls -al /etc/portage/
total 6
drwxr-xr-x 10 root root 328 Feb 22 21:18 .
drwxr-xr-x 78 root root 4568 Feb 23 18:02 ..
-rw-r--r-- 1 root root 0 Feb 22 21:18 .keep_sys-apps_portage-0
drwxr-xr-x 2 root root 80 Feb 22 18:57 bin
drwxr-xr-x 2 root root 464 Feb 22 17:43 package.keywords
drwxr-xr-x 2 root root 80 Feb 3 02:27 package.mask
drwxr-xr-x 2 root root 504 Feb 22 17:44 package.unmask
drwxr-xr-x 2 root root 680 Feb 18 06:20 package.use
drwxr-xr-x 2 root root 80 Feb 22 18:57 postsync.d
drwxr-xr-x 3 root root 72 Dec 11 17:09 savedconfig
drwxr-xr-x 2 root root 72 Feb 16 19:10 sets
root@fireball / #
I created the package.* ones and I think I did the sets one too. I
haven't messed with the others tho.
I wonder if the devs know about all this? Is this something they should
know about? Is this unique to me? I have KDE installed by using the
kde-meta but surely I'm not the only one that uses it.
Dale
:-) :-)
