extragear/multimedia/amarok

[Lydia Pintscher]

On Mon, Feb 2, 2009 at 20:19, Erik Hovland <erik at hovland.org> wrote:
> No, but showing a bit more restraint might have been prudent. Note that not even
> kubuntu has readily available packages for 4.2 on intrepid. So that
> means that if
> someone wants to now develop w/ Amarok they have to once again get on the
> KDE source code train. Not a pleasant proposition for those of us who would
> prefer to only work on Amarok and deal w/ its bugs.
>
> Having said that, the deal is done - I say don't revert it. Better I
> struggle in the
> background if the rest of the devs are already clipping away on 4.2. I am likely
> to just not 'git svn rebase' for a couple of weeks until kubuntu catches up.

Kubuntu does have 4.2 packages for intrepid. See kubuntu.org for how
to get them.

>> 3)
>> The only reason for the dependency on KDE 4.2 is currently LibPlasma.
>> We do have the option of importing the latest LibPlasma into Amarok,
>> as we used to do. Later on, we could still decide whether we want to
>> keep this or not; changing this would be trivial.
>>
>> yes, the reason to do this is to remove the temporary hack that is copying
>> libplasma in our source tree. by doing this we lose out on bugfixes, need to
>> make sure that things don't get out of sync, and add more work for ourselves
>> in the future.
>
> One of the reasons for the switch was because staying on the tip of plasma was
> more trouble then the benefit of getting the bugfixes. Is anyone sure that these
> troubles are over? I know they moved to kdelibs and have pledged a stable API,
> but "the proof is in the pudding."

They made a big effort before 4.2 release to get everything in shape
and I don't know of any problems so far. So I think that is ok.


Cheers
Lydia

-- 
Lydia Pintscher
Amarok community manager
kde.org - amarok.kde.org - kubuntu.org
claimid.com/nightrose