On Tue, 10 Jan 2006 20:48:14 -0500, Arthur Hagen wrote:

> Peter <peter@localhost.com> wrote:
>>
>> The question I have is since I am no longer relying on KDE, do I need
>> the KDE use variable which seems to be set automatically. Could I pud
>> -kde in my make.conf file? Would that hurt the few KDE apps I have or
>> future upgrades for them?
>
> What -kde will do is remove kde support/linkage/pullins for apps where kde
> is optional. If you emerge something that *requires* kde, kde will still
> be pulled in (but it will no longer be announced as available).
>
> To see which packages will be affected, and if you have gentoolkit
> installed, do "equery hasuse kde".
> If setting -kde in USE, you should rebuild these with --newuse, to have
> them built without kde dependencies.
>
> After doing all this (including the rebuild with --newuse), you might want
> to do "emerge --pretend --depclean" to see what packages you might now be
> able to remove. "emerge --depclean" isn't 100% safe, so if you decide to
> run it, I'd recommend doing "emerge --update --newuse --deep world" and
> "revdep-rebuild" afterwards, like the WARNING states.
>
> Regards,

Interestingly enough, only the ONE package I cited in the bug report
showed up in equery, rss-glx. I grep'ped portage and a handful of apps
came up, none of which I use. So, I suppose I can go ahead and put -kde in
make.conf safely.

Was this documented somewhere? I wish it was. Seems like there are way too
many use flags. JMHO.

Thanks for the tip.