media-sound/amarok-2.6.0 depends on =media-libs/liblastfm-0.3* media-sound/tomahawk-0.5.5 depends on >=media-libs/liblastfm-1.0.1 I propose separate slots for <media-libs/liblastfm-1.0 and >=media-libs/liblastfm-1.0 to solve this issue.
It's not always possible to slot a package without messing with the build system. Of course, the amarok dependencies might be a bit too strict
From the amarok README, dependencies section: * Liblastfm 0.3 (1.0 or newer is incompatible, porting is pending for Amarok 2.7) So the amarok dependency is stuck as it is, unfortunately, at least until 2.7 is released. And I don't think it's feasible for us to maintain slotted liblastfm, since that would indeed require a lot of fiddling with the build system and would probably break other packages. I'd suggest just disabling liblastfm on one or the other for the moment.
Since I’m the only one who complained so far, I’m OK with waiting for Amarok 2.7 and will close this bug. If someone else finds this annoying we can just re-open it.
(In reply to comment #3) > Since I’m the only one who complained so far, I’m OK with waiting for Amarok > 2.7 and will close this bug. > > If someone else finds this annoying we can just re-open it. I'm going to try to backport the liblastfm dep changes from amarok trunk. I've asked on #amarok and learned some distributions are doing that. In the meantime, can you please test amarok-9999?
I dont think we need this bug anymore since amarok-2.7.0 is now in ~arch.
