[Development] Deprecating modules with 5.5

Allan Sandfeld Jensen kde at carewolf.com
Fri Feb 6 00:15:48 CET 2015

On Friday 06 February 2015, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Thursday 05 February 2015 21:39:16 Allan Sandfeld Jensen wrote:
> [snip]
> > > [0] <https://www.debian.org/security/2015/dsa-3148>
> > 
> > It would have been the same problem with WebKit. Neither Google nor Apple
> > cares about supporting any build environment more than 1-2 years old.
> > When we still was part of WebKit, Digia were the ones supporting the at
> > the time most widely used OS X release 10.6 because Apple did not, and
> > that on top of support all Windows versions which Apple doesn't care
> > about those either.
> Yes, this is true, and actually one of the reason I don't want to spend my
> time in packaging this web stuff :)
> > And as you might remember PowerPC turned out to have been broken in
> > QtWebKit's JavaScriptCore 5.0 to 5.3, and no one noticed, and those
> > changes are not even upstreamable because Apple doesn't care.
> But at least there we could just disable JIT, which is what we did. When we
> had V8 around (if I remember correctly it was used for QML, but my memory
> might be failing me) we couldn't.

The problem with PowerPC was that the non-JIT fallback was not working on big 
endian machines, which was not discovered by any of the regularly tested 
platforms and configurations. I meant it as an example that having a non-JIT 
fallback doesn't seem to help much because so few people use it that it is not 
even discovered when it compiles but crashes on run.

About QtWebEngine, do you know what system libraries you have problems with it 
duplicating? I think we can configure most of it in the build system and 
already follow the Qt build settings for some that are usually shipped with 


More information about the Development mailing list