the right home for Phonon

Matthias Kretz kretz at kde.org
Thu May 29 17:31:45 BST 2008


On Thursday 29 May 2008, David Faure wrote:
> On Thursday 29 May 2008, Matthias Kretz wrote:
> > On Thursday 29 May 2008, Thiago Macieira wrote:
> > > On Thursday 29 May 2008 09:13:53 Matthias Kretz wrote:
> > > > And I'm still not fully happy with phonon trunk in kdesupport and the
> > > > release branches in branches/phonon. Because many KDE developers will
> > > > just install kdesupport and not test the code in branches/phonon
> > > > which is going to be released. The only idea to improve that
> > > > situation would be to again use a dedicated phonon module and use
> > > > svn:externals to link either a release branch or trunk to
> > > > kdesupport... but I don't know if an external really is an
> > > > improvement.
> > >
> > > Why are there modifications in trunk that are not in 4.2?
> >
> > Because the stuff in trunk is not ready for a release.
>
> I think the real question is: why doesn't qt-copy-4.1's phonon have the
> stuff that is in branches/phonon/4.2. This is what causes the compilation
> error.
> From your reply I assume the answer is: qt-4.1's phonon is not recent
> enough, but then you write "Trolltech is free to use the 4.2 branch or even
> the 4.1 branch", which confuses me. If TT keeps using the 4.1 branch,
> kdebase will never compile with Qt's phonon, will it?

Ok, that might have been too confusing to start with that topic. So yes, 
phonon 4.1 is incompatible to current kdebase and it will stay that way. And 
Qt 4.5 should ship phonon 4.2 or later if at all possible.

> > The only idea to improve that situation would be to again use a
> > dedicated phonon module and use svn:externals to link either a release
> > branch or trunk to kdesupport...
>
> No, a much simpler idea would be:
> kdesupport/phonon contains whichever phonon stable-branch is needed for the
> rest of KDE branches/work/phonon/trunk or something like that is where
> unstable phonon features are developed

I don't like a branches/.../trunk. Then I'd rather use trunk/phonon.

latest phonon-stable == branches/phonon/<max>, which is why I suggested an 
svn:external. I neither want to merge from branches to kdesupport all the 
time, nor do I want to move from kdesupport to branches whenever a new branch 
starts.

> David (still without a compiling kdebase)

compile and install phonon from kdesupport and it'll work. Or, preferred:
svn co $KDESVN/branches/phonon/4.2 phonon
and install that.

-- 
________________________________________________________
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/20080529/2fc30225/attachment.sig>


More information about the kde-core-devel mailing list