Since the introduction of the split ebuilds for KDE, amarok (1.2.1) won't be able to ompile if, prior to that, you don't emerge kdebase/kdemultimedia-arts. therwise, configure will complain: ================================== === AMAROK WILL NOT BE BUILT ================================================ ================================== = = No suitable multimedia framework was detected. You need to install at least = one of the supported frameworks as detailed in the amaroK README. = If you are thinking, 'I have aRts you stupid configure!', then you probably = need to install kdemultimedia-devel. = [...] I'm not sure as to why portage accept to emerge it anyway, desite having not emerge a thing in kdemultimedia. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Well, kdemultimedia-arts _is_ listed as a dependency...
(Yannick, please use the web interface to reply) I think I'm getting what's going on: you have kdemultimedia-3.3 installed, so portage thinks that all the dependencies are satisfied, but since you are compiling for kde-3.4, having kdemultimedia-3.3 is not enough... This problem could happen also in previous releases, but probably only happened very rarely, so it was not a big issue. With split ebuilds, perhaps we will see it a bit more frequently? Anyone can see an easy solution for it?
Yes, I think this is what happenned. From my understanding, this bug will be triggered when a user upgrade to a new version of kde that use a new slot *and* goes from using the meta packages to using the split ebuilds. Maybe the amarok ebuild needs to be sure that the kdemultimedia-arts package that is installed is the same version than kdelibs to witch amarok will be linked against. Hope you get what I mean.
another reason to just force a xine-lib dep if no engines are installed ;)
*** Bug 88298 has been marked as a duplicate of this bug. ***
*** Bug 105204 has been marked as a duplicate of this bug. ***
Hm, old bug and Xine is default in latest ebuilds.
