Dear Maintainer,

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.

And no, not everyone ported to Qt5, yet. :-)

Regards,

Hendrik Sattler

severity 816250 wishlist
tag 816250 wontfix
thanks

On Monday 29 February 2016 07:51:35 Hendrik Sattler wrote:
[snip]


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.

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.

This sounds like a good reason to start with the porting :)

Sorry, but if you really need the multimedia bits you should really consider
using Qt5.

Kinds regards, Lisandro.

severity 816250 wishlist
tag 816250 wontfix
thanks

On Monday 29 February 2016 07:51:35 Hendrik Sattler wrote:
[snip]


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.

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.

This sounds like a good reason to start with the porting :)

Sorry, but if you really need the multimedia bits you should really consider
using Qt5.

Kinds regards, Lisandro.

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>:

Etra dependencies are libasound. Wow. Unresolvable. Either you did not even try or you must be joking.

Qt4.8 is still maintained until 5.6 is really released although only minimal. And it does not get immediately obsolete even then.

Haha. Is that really the policy of Debian to cripple libraries to enforce extra work?

Please uncripple Qt4 in Debian! And please read the Qt4 Debian changlog on the initial nonsense that lead to this bug report.

HS

No I didn't. I won't re add/start compiling again a Qt 4 module for the
reasons I wrote in my previous mail.

If you need the functionality you should really consider switching to Qt 5

-- 
Greeting,

I have access to very vital information that can be used to
move huge amounts of money.

If it was possible for me to do it alone I would not
have bothered contacting you. Ultimately I need you to play an
important role in the completion of this business transaction.

Regards,
Mr Alexander Bulyanda