openSUSE are doing it, we should probably too. I've begun to set it default off in my packages whenever it was the option. Last commit in upstream repository happened 15 months ago.
+1
In addition to $URL, packages that depend on PyQt5[webkit]: dev-python/QtPy-1.4.0-r1[webkit] dev-python/spyder-4.0.0_beta1[webkit] media-sound/frescobaldi-3.0.0 media-video/openshot-2.4.0-r1 sci-mathematics/relational-2.5 sci-geosciences/qgis-3.4.7[webkit] dev-util/eric-18.03 app-text/openlp-2.4.6 app-text/calibre-3.41.3
No need to hurry, new release is coming in the next few days
Are you aware of https://github.com/annulen/webkit/commits/qtwebkit-5.212 ? That's where most of effort re webkit is going right now as far as I can tell. Also, I've chatted with an opensuse maintainer, he's not aware of any plans to ditch qtwebkit.
(In reply to Georg Rudoy from comment #4) > Are you aware of https://github.com/annulen/webkit/commits/qtwebkit-5.212 ? > That's where most of effort re webkit is going right now as far as I can > tell. Yes, we're aware. That repo had been almost dead for more than a year until development restarted less than a month ago.
(In reply to Georg Rudoy from comment #4) > Also, I've chatted with an opensuse maintainer, he's not aware of any plans > to ditch qtwebkit. They've dropped it from default installs.
Porting guide: https://doc.qt.io/qt-5/qtwebenginewidgets-qtwebkitportingguide.html
Upstream seems relatively active these days... "annulen Merge branch 'qtwebkit-stable' into qtwebkit-5.212 … 5a4cfb5 11 days ago" Would be nice to get a bump to fix the build with Qt 5.15...
(In reply to Luke-Jr from comment #8) > Upstream seems relatively active these days... Years later the only release is still at alpha. (In reply to Luke-Jr from comment #8) > Would be nice to get a bump to fix the build with Qt 5.15... Builds fine, not one bug recorded wrt, file one if you got one.
(In reply to Andreas Sturmlechner from comment #9) > (In reply to Luke-Jr from comment #8) > > Upstream seems relatively active these days... > Years later the only release is still at alpha. Hey, I didn't say it was safe/secure, just active! :) (QtWebEngine probably isn't either. I tracked the Magellian vulnerability for over a year, and it didn't get fixed before I gave up.) > (In reply to Luke-Jr from comment #8) > > Would be nice to get a bump to fix the build with Qt 5.15... > Builds fine, not one bug recorded wrt, file one if you got one. Still investigating nature of it. It may simply be that qtwebkit needs rebuilding after upgrading Qt. (and didn't automagically)
Please limit the chatter to QtWebKit, thanks. (In reply to Luke-Jr from comment #10) > Still investigating nature of it. It may simply be that qtwebkit needs > rebuilding after upgrading Qt. (and didn't automagically) This is tracked in bug 661052.
(In reply to Luke-Jr from comment #10) > > (In reply to Luke-Jr from comment #8) > > > Would be nice to get a bump to fix the build with Qt 5.15... > > Builds fine, not one bug recorded wrt, file one if you got one. > Still investigating nature of it. It may simply be that qtwebkit needs > rebuilding after upgrading Qt. (and didn't automagically) Yes, rebuilding qtwebkit fixed it. So probably it just needs some tweak to make it automagic.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6d369a03bd098977934052a920611dd35fe91805 commit 6d369a03bd098977934052a920611dd35fe91805 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2020-11-20 22:37:19 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2020-11-20 22:42:03 +0000 profiles: Add dev-qt/qtwebkit to package.deprecated Bug: https://bugs.gentoo.org/684580 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> profiles/package.deprecated | 4 ++++ 1 file changed, 4 insertions(+)
Many QGIS necessary plugins depend on qtwebkit. Sad but true. Really I cannot work without them. Now I manually edit the qgis ebuilds to use webkit in src_configure(). Please, let users to choose if they need. System is for work not just for beauty.
(In reply to UlvHare from comment #14) > System is for work not just for beauty. That's not really the question here. It is unmaintained and the paint is coming off. Any future bison/boost/glib/python update (those are only examples for which we already have to patch the current version) can be the final death nail.
