qtphonon's status.

[marius.storm-olsen at nokia.com]

On 5/18/12 10:14 AM, "ext Thiago Macieira" <thiago at kde.org> wrote:

>On sexta-feira, 18 de maio de 2012 05.54.10, marius.storm-olsen at nokia.com
>wrote:
>> 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.
>
>I disagree. At this point, we don't know what the Phonon developers want
>to do 
>with their API in Qt5, whether they want to keep API compatibility or
>not. The 
>decision to do that for Qt was our own and does not necessarily imply the
>same 
>for Phonon.
>
>I'd love them to, but if they have different plans and little manpower,
>we 
>can't force them to keep the API.
>
>Until the Phonon maintainers speak up and let us know what their plans
>for Qt 
>5 are, we should consider our qtphonon.git module a disservice to
>everyone. If 
>none of them speak up, I recommend removing the module from the build
>process.

We did promise a minimal migration path from Qt 4 to Qt 5, and removing
the phonon module from qt5.git, with no easy way of compiling up the
current upstream phonon with Qt 5 goes against this promise. That's why I
think we should keep it, until upstream has given a clear message of how
to proceed for Qt 5 users of phonon. (1. What their direction is, 2.
Migration path for Qt 4 users, 3. Build instructions for Qt 5 users on all
T1 platforms, etc)

Until then, at least Qt users can use phonon as is, just like they do in
Qt 4.

-- 
.marius