Bug#816250: qt4-x11: Build Qt4 Multimedia module (QtMobility not in Debian anymore)
Hi,
you obviously misunderstood the intention of the bug report. It's not about reintroducing QtMobility but compiling Qt4 with the modules it provides instead of crippling it on purpose.
Am 29. Februar 2016 12:59:11 MEZ, schrieb "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer@gmail.com>:
>severity 816250 wishlist
>tag 816250 wontfix
>thanks
>
>On Monday 29 February 2016 07:51:35 Hendrik Sattler wrote:
>[snip]
>> Although not very welcome in the past, it was at least possibly to
>use
>> classes from Qt4 Multimedia module in Debian when using QtMobility
>> MultmediaKit. The latter was removed from Debian and the former was
>not
>> built because the latter was in Debian. This obviously changed, so
>the
>> reasoning for not building Qt4 Multimedia module is not valid
>anymore.
>
>
>The mobility stack was removed because it was buggy and had a handful
>of
>rdeps, which we've got to remove. If it had just a few rdeps then it's
>not
>that needed, and the same could be said for the multimedia stack.
Etra dependencies are libasound. Wow. Unresolvable. Either you did not even try or you must be joking.
>Qt4 is dead upstream in all senses. So a non upstream-supported stack
>is
>indeed a very good reason to avoid reintroducing it to the archive.
Qt4.8 is still maintained until 5.6 is really released although only minimal. And it does not get immediately obsolete even then.
>> And no, not everyone ported to Qt5, yet. :-)
>
>This sounds like a good reason to start with the porting :)
Haha. Is that really the policy of Debian to cripple libraries to enforce extra work?
>Sorry, but if you really need the multimedia bits you should really
>consider
>using Qt5.
Please uncripple Qt4 in Debian! And please read the Qt4 Debian changlog on the initial nonsense that lead to this bug report.
HS
Reply to: