Alan McKinnon wrote:
On Saturday 20 December 2008 08:27:40 Nikos Chantziaras wrote:
emerge -av --depclean:
kde-base/kopete
selected: 3.5.10
protected: none
omitted: 4.1.3
kde-base/kget
selected: 3.5.10
protected: none
omitted: 4.1.3
kde-base/kmenuedit
selected: 3.5.10
protected: none
omitted: 4.1.3
The list goes on. All those packages are in my world file. This only
started happening after installing KDE 4.1.3. Another nice effect of
not putting KDE4 in new portage trees but rather mixing them with KDE3?
What can I do?
You can start by giving the relevant information, like what exactly related to
kde is in world?. Chances are you only have KDE there, and emerge will
probably want to nuke all but the latest SLOT. Common problems with KDE:
Put 'kdeprefix' in USE and rebuild
Put KDE:3.5 in world and recheck.
This last one often needs to be redone recursively to get everything in world
that needs to be there. I've heard that autounmask helps with this
kdeprefix has nothing to do with KDE3. It's not needed. It's only
needed to have many KDE4 versions at the same time.
I'll try the KDE:3.5 thingy. I wonder though why the heck I have to do
this. KDE4 should have been put in its own tree.
