the right home for Phonon

[Diego Iastrubni]

The difference is that libpng and freetype are statically linked into Qt at 
some configurations, while Phonon not only depends on Qt, but it will be 
always a dynamic library.

I don't understand how this will work, a special --configure flag 
(--use-external-phonon-source?)
how do you bootstrap it? (qt needs phonon, phonon needs qt), this time I am 
talking from the packaging side of point, as I am not sure it's a good idea 
to have a phonon-source package in debian.

The same problem happens with QtWebKit, as IMHO, it will also have a different 
release cycle, independent of Qt itself. Well, I assume Trolltech/Nokia have 
more control over that one.

On Friday 16 May 2008 00:00:56 Matthias Kretz wrote:
> On Thursday 15 May 2008, Diego Iastrubni wrote:
> > On Thursday 15 May 2008 22:17:38 Alexander Neundorf wrote:
> > > > Open questions:
> > > > a) should kdelibs 4.1 contain libphonon or should it depend on an
> > > > external libphonon?
> > >
> > > I'd say that kdelibs should depend on libphonon from kdesupport. May
> > > bring more users for phonon.
> >
> > What happens when someone installs Qt 4.4.x? he will have 2 different
> > libphonon.
>
> That's the situation we have now. And that's what we want to fix: make
> kdesupport the place where libphonon lives. The copy in Qt is then in there
> just for convienience like libpng, libjpeg and such.