Hey,

kdepim in now on the track to release a Qt5 version in August. kdepim has a 
dependency on QtWebEngine. 

> Of course I won't stop anyone in trying to ship it. But if no one steps up
> to maintain it I will not hesitate in simply ignoring it as much as
> possible, even at the point of not shipping stuff that depends on it.

I'll stand up to ship it :)

Regards,

sandro

--
Am Freitag, 10. Oktober 2014, 00:19:51 schrieb Lisandro Damián Nicanor Pérez 
Meyer:
> As you might know, Digia plans to ship QtWebEngine as a kind of replacement
> for QtWebkit on 5.4.
> 
> I have just had a chat with one of Fedora's maintainers and discussed some
> of the "key" points on QtWebEngine. Note that I only checked some of the
> following, feel free to pin point whatever you fell/like.
> 
> - It uses V8 (the same we got rid some months ago from qtdeclarative) which
> doesn't builds on all archs.
> 
> - It bundles ffmpeg and it seems not easy to use an external (system) one.
> In case we still have it in the archive for Jessie+1.
> 
> - Bundles even more stuff that webkit
> 
> - It's not a drop-in replacement for QtWebkit
> 
> - It will mean another copy of the code in the archive, apart from Chromium
> itself
> 
> - QNetworkAccess support is gone (no KIO nor Qt's http code)
> 
> So my *personal* plan for Jessie+1 is this: not loose a single second on
> QtWebEngine.
> 
> Of course I won't stop anyone in trying to ship it. But if no one steps up
> to maintain it I will not hesitate in simply ignoring it as much as
> possible, even at the point of not shipping stuff that depends on it.
> 
> Cheers, Lisandro.

Attachment: signature.asc
Description: This is a digitally signed message part.

-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Reply via email to