[Development] New Qt 5.7.0 RC snapshot available
Kai.Koehne at qt.io
Wed May 18 17:04:24 CEST 2016
> -----Original Message-----
> From: Development [mailto:development-bounces+kai.koehne=qt.io at qt-
> project.org] On Behalf Of Ralf Nolden
> I suggest having a look at https://bugreports.qt.io/browse/QTBUG-49883
> and do some consideration how to handle those issues. If modules are
> deprecated but should still work for backwards compatibility, then there
> should be no change at all that prevents that.
There's a difference between deprecated and unsupported.
Deprecated means we don't advice you to start _new_ projects with it,
Otherwise it has the same promises as any other module.
Unsupported means it's not part of Qt anymore.
> Otherwise that module is
> "somewhat supported even if we don't like to" - which creates a really
> confusing situation for packagers and porters, but (at least I) can live with
> that as long as we get updated (tagged) release tarballs :)
QtQuick1 and QtWebKit are _not_ supported anymore since Qt 5.6.
What we have said is that we will provide QtWebKit source packages as courtesy
on a best-effort basis. That is, also the QtWebKit source package under
is not part of Qt anymore, and not supported. Use it at your own risk.
There's also no promise we can continue providing these.
> So, an updated tarball for qtquick1 for 5.6 would be really much appreciated
> (so that it works with 5.6.x and 5.7.x)
It's the first time I hear someone asking for a tarball for QtQuick1.
I see that people are still stuck with WebKit for some use cases, because the
architecture, OS requirements and API of WebEngine differs. For QtQuick,
it's IMO really painless to update. Also, last time I checked, there were very
little Linux packages left that still require Qt Quick 1. So what's your use
More information about the Development