Created attachment 581880 [details] Updated ebuild No patches needed - everything was applied in upstream.
Still an alpha release?
There are a few things that would be better to fix before making "real" release [1]. Still, there are no real showstoppers, and if it was a regular piece of software, not browser engine, I would dub this release as 5.212.0 just to acknowledge that it works. But I don't want to give people false sense of security, as underlying WebKit code was not updated. We are in process of making such update and it will result in a stable version with proper ".0" release. [1] https://github.com/qtwebkit/qtwebkit/issues?q=is%3Aopen+is%3Aissue+milestone%3Av5.212.0-beta (These things are expected to be fixed soon)
(In reply to Konstantin Tokarev from comment #2) > But I don't want to give people false sense of security, as underlying > WebKit code was not updated. We are in process of making such update and it > will result in a stable version with proper ".0" release. Is there an ETA for that? I haven't looked yet at the delta between our pre20180120 and alpha3, and I wonder if it's worth the upgrade if the underlying WebKit code has not changed.
There was a number of bug fixes
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/qt.git/commit/?id=b85921e28a39466ec5cd12c167b58f1c115b9390 commit b85921e28a39466ec5cd12c167b58f1c115b9390 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2019-07-06 07:59:01 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2019-07-06 10:26:44 +0000 dev-qt/qtwebkit: Add 5.212.0_pre20190629 aka alpha3 for testing, EAPI-7 Bug: https://bugs.gentoo.org/689224 Package-Manager: Portage-2.3.68, Repoman-2.3.16 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> dev-qt/qtwebkit/Manifest | 1 + dev-qt/qtwebkit/metadata.xml | 27 ++++ .../qtwebkit/qtwebkit-5.212.0_pre20190629.ebuild | 140 +++++++++++++++++++++ 3 files changed, 168 insertions(+)
>Is there an ETA for that? Something of early preview quality is expected to be available in ~1 month. There is no ETA for full-featured release ready to be used in distros, it depends on not yet known amount of bug fixing and overall performance of team (if I was working alone I would say something like "no less than 6 months from here")
