Phonon-4.4; KDESupport-4.4

James Tyrer jrtyrer at
Sun Feb 14 17:17:45 GMT 2010

James Tyrer wrote:
> James Tyrer wrote:
>> You can now obtain a Phonon-4.4.0 release, or at least a stable RC.
>> You should use the KDE Phonon release rather than the one the comes with Qt.
>> IIUC, KDE Phonon is never actually released except in the SVN archives. 
>>   For some reason you will not find it where it would be expected in 
>> "/tags/phonon" but it is available here: "/tags/kdesupport-for-4.4/phonon".
>> I still recommend that if you are building from source that you checkout 
>> the whole "/tags/kdesupport-for-4.4" directory rather than downloading 
>> the individual packages.  Except that you should still not install QCA 
>> from KDESupport (it will not install if you build the tree from the: 
>> "kdesupport-for-4.4" directory), but rather download the tarball.
>> Note that although this is a TAG, that the previous KDESupport TAGs have 
>> been updated (another reason to use SVN) so you should check for updates.
>> I have updated the build tutorial:
>> following the release of KDE-4.4.0
> My patience is wearing a bit thin.  We are clearly lacking TQM.
> The SVN for KDE-Support-4.4 is seriously broken DO NOT USE IT.
> USE:
>       svn co svn:// -r1087679
> This is, I think, what KDE-Support-4.4 should be.
> David Faure, please fix this.
Have to say that I don't understand KDE politics.  I am an engineer and
don't think that there should be any.  This problem should never have
occurred and it wouldn't have occurred it there was a proper TQM plan in

IAC, someone else fixed the problem.

Tom Albers, thank your for promptly fixing this.

You now get Phonon-4.4 when you checkout: "/tags/kdesupport-for-4.4".
Although I should note that it appears that it is only the first Beta,
since someone was concerned about having a stable version.  This doesn't
seem exactly the best that the new release of KDE-4.4.0 should be
dependent on a Phonon Beta, but that is the way it is.  I hope that it
will be updated in SVN although it is a TAG when it should be a BRANCH.

My patience has been severely tried lately in my efforts to maintain the
build instructions:

There were issues first with Redland, then Virtuoso and now this.  ARGH! :-D

If I am to continue to do this, I will need some help from the
developers at least to the point that I need access to information.
Trial and error is not a satisfactory method.

I don't think that this needed information is being deliberately kept
secret, but the result is the same.  What is the point of releasing
tarballs of the code if it isn't possible for users to build them.

James Tyrer

Linux (mostly) From Scratch
This message is from the kde mailing list.
Account management:
More info:

More information about the kde mailing list