[Development] qtphonon's status.

marius.storm-olsen at nokia.com marius.storm-olsen at nokia.com
Fri May 18 07:54:10 CEST 2012

This probably means we should keep the old repo there for backwards
compatibility, and with documentation stating that the module is old and
out-of-date, and where and how they can get a more recent version.

We shouldn't mix build systems in qt5.git itself. If other add-ons decide
to use cmake as their build system, that's fine; but any module aiming to
be part of qt5.git will need to use the same build system as the rest of
the modules of qt5.git. (This will also be true for whatever build system
we move to at some later point.)

Distros of course should bundle Qt with the latest version from upstream.


On 5/17/12 11:50 PM, "ext Olivier Goffart" <olivier at woboq.com> wrote:

>On Thursday 17 May 2012 21:42:03 Thiago Macieira wrote:
>> On quinta-feira, 17 de maio de 2012 19.03.30, lars.knoll at nokia.com
>> > >What's the difference between webkit and phonon in this regard?
>> > 
>> > Webkit isn't hosted on qt-project neither, so removing it from
>> > is the right choice if it's being developed somewhere else.
>> The "qt5-module.git" repository of Qt WebKit is a branch of the webkit
>> that contains the latest version supposed to work with Qt. It's not
>> the same thing.
>> If the Phonon devs do the same for qtphonon.git, I don't see a problem
>> keeping the repository around. That's not the current situation.
>The phonon upstream repository is itself modularized into several sub-
>repositories (core + one per backend)
>Also, as I pointed out, the upstream phonon requires cmake for building.
>It could theoretically be possible to create the qmake .pro files, but
>someone will need to maintain them.
>(I personaly think it is fine to have add-ons requiring cmake. But I
>know about qt5.git)
>Woboq - Qt services and support - http://woboq.com
>Development mailing list
>Development at qt-project.org

More information about the Development mailing list