move Phonon to trunk kdelibs (another branch to merge)

[Matthias Kretz]

On Tuesday 14 March 2006 15:17, Kevin Ottens wrote:
> In my opinion, it's important to keep them outside of kdelibs because it's
> generally better to be in sync with the other project releases (in order to
> avoid incompatibilities because of ABI changes in those projects, etc.)

This is probably also a question of on which side will be more changes. For 
example if a backend is developed for gstreamer 0.10, the backend will not 
have to change until a gstreamer 0.12 or 1.0 is released. And then this will 
be a new backend anyway. (Phonon will then be able to use either 
Phonon-GST-0.10 or Phonon-GST-1.0.) On the other hand I expect changes in 
Phonon after the release of KDE 4.0 that will need changes in the backends to 
be supported (KDE 4.1 can still use old backends, but the new functionality 
cannot be used then).

> Maybe for the backends that will stay in KDE repository, we should have a
> special module (let's call it "kdelibs-volatile") indicating that they are
> tied to other release cycles (maybe extragear could be this
> "kdelibs-volatile" since it's already not tied to kde release cycle).

extragear might actually be a good place for the backends. But as I said, I 
expect that the backends need to get updated with new versions of KDE rather 
than with new versions of the media framework.

-- 
C'ya
        Matthias
________________________________________________________
Matthias Kretz (Germany)                            <><
http://Vir.homelinux.org/
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060314/9ae913dc/attachment.sig>