Dale writes:
> 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.
I see "inherit kde4-meta" in the khelpcenter ebuild, but I don't know
what inherit means here.
> 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.
@system also pulls in some KDE stuff here. I don't have time to fully
investigate this, after a short look it seems to me that gawk pulls in
gettext, that needs git, git wants subversion, and that has the kde USE
flag. So subversion pulls in kwalletd and kdelibs, and those need some
more KDE stuff.
Looks like normal behaviour to me. @system should be a small set, but
when some packages in @system have kde USE flags, they will pull in KDE
stuff.
Wonko
