Sabayon 4: Unwanted kde 4 dependencies

[gnac]

It seems that Sabayon 4 has unmasked a lot of packages, eg amarok, yakuake and others from the looks of this board, that depend on kde 4.1. Shouldn't these packages be masked in favour of 3.5.10 apps?

[micia]

I think that who actually want to install KDE4 has
to be able to do it with equo, without having to unmask
and doing such things.
I am not a developer, and this is just my opinion.

I never experienced any "unwanted" KDE4 dependencies, because
amarok, yakuake, and so on have their 3.5 and 4.1 package

[gnac]

KDE4 is currently masked.

My suggestion is that slotted kde applications like amarok which are not masked should default to the kde 3.5 version.

As it stands, the casual user (i.e. using unmasked KDE 3.10) who types

Code: Select all

equo install amarok

will install the kde 4 version and as a consequence pull in all the kde4 dependencies. Post install, Amarok will also not work from a command line or run dialog because the kde4 location is not in the path unless the path is manually added. Having both kde 3.5 and kde 4 on the path is undesirable.

It would be preferable that as long as KDE 4 is masked, equo should default to the 3.5.10 branch of slotted applications like amarok. Eg equo install amarok should install the 3.5.10 version of that application by default. If the user want the 4.x branch of a package, that is still accessbile by using the fully qualifying package name, eg

Code: Select all

equo install media-sound/amarok-2.9-r1

[joost]

amarok is an exception.

Normally you cannot have both versions in the tree (our serverside tree i mean) because they cause collisions on files they both have.

We used portage to compile and package it (using emerge -B) and that we added to the entropy tree to make both available.
This package is the only exception.



(from the amarok-2.0 ebuild)

!kdeprefix? ( !media-sound/amarok:0 )