the right home for Phonon

[Matthias Kretz]

Hi,

this morning Thiago, Dirk and I were talking about where the Phonon code 
should live and who should release and ship what.

This is what we agreed on:
- move libphonon (+examples, docs and tests) and all backends that don't
  depend on kdelibs (i.e. all that are in kdereview atm, but not xine) to
  kdesupport/phonon
- phonon will (in theory) release indepently from kdelibs and Qt
  - branches will be in branches/phonon
  - tags will be in tags/phonon
  - phonon releases will probably be in sync with KDE and Qt releases, but may
    skip one or add one if needed
- phonon code that depends on kdelibs (KCM, Platform plugin, xine backend,
  future gst backend KCM) all go to kdebase/runtime/phonon and release
  together with kdebase (no more, no less)
- libphonon translations are merged into kdelibs package and released with
  kdelibs
- kdesupport/phonon never freezes. Freezes happen only in branches/phonon

Open questions:
a) should kdelibs 4.1 contain libphonon or should it depend on an external
   libphonon?
b) how should the Qt build work with (external) libphonon depending on Qt, but
   QtWebKit depending on libphonon in the future

Comments?

I'd like to do the necessary moves one of these mondays.

Oh, and I'll need buildsystem testers/helpers, especially for Win and Mac.

-- 
________________________________________________________
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: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080515/97ccc78c/attachment.sig>