* Lisandro Damián Nicanor Pérez Meyer <perezme...@gmail.com> [2015-06-25 
11:41:25 -0300]:
> > > > Seeing that Qt removes QtWebKit from their source-
> > > 
> > > Actually they are not going to update it anymore, maybe except for
> > > security
> > > bugfixes. The source will remain there and should be able to keep building
> > > with Qt5.6+
> > 
> > I'm not entirely sure it will, unfortunately.
> > 
> > From [1]:
> > 
> > * We’d still remove the deprecated modules from our Qt 5.6 release
> >   (maybe with the exception of Qt Script).
> > 
> > I also remember reading somewhere explicitely that it won't be
> > included in the qt-everywhere-opensource-... archive - sadly I can't
> > find the mail anymore.
> 
> We are building from the submodules tarballs, so we already have the source 
> code available. Building from qt-everywhere would be highly painfull: if 
> something fails everything fails.

I see - it seems some confusion just got cleared up:

https://codereview.qt-project.org/#/c/115267/1//ALL,unified

- The QtWebKit, QtScript modules and support for the QML 1 language and
  QtQuick 1 are deprecated and Qt 5.6 will be the last release to
  include them. Starting with Qt 5.7, the source code for those modules
  will not be included in Qt's packaging. Compiling the 5.6 release of
  those modules along with Qt 5.7 or future versions should work.

> > The series of patches they have on top of Chromium look a lot more
> > sane. But I see how having what's essentially a Chromium fork is
> > problematic :-/
> 
> Right :-/

Unfortunately if I understood correctly upstreaming those patches also
isn't a viable alternative, as Chromium doesn't want this kind of
Qt-specific code in its tree...

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/

Attachment: pgprAtYr0Kvo3.pgp
Description: PGP signature

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

Reply via email to