On Tue, 2017-01-31 at 11:29 +0000, Christian Stadelmann wrote: > The same should probably be done for qtwebkit (Qt4) and qt5-qtwebkit > (Qt5) …. Is there any procedure for this? I cannot find the F27 > proposed change to remove webkitgtk and webkitgtk3 either. The reason I proposed holding off on removing QtWebKit is that there is an active QtWebKit fork that we can switch to soon, instead of relying on the insecure QtWebKit distributed by the Qt project. There is no release yet, but one is coming soon. It will be based on WebKitGTK+ 2.12, which means it will still have dozens of security bugs, but way fewer than upstream QtWebKit, so it's at least a huge improvement over the status quo; an update straight to future WebKitGTK+ 2.16, skipping the current version 2.14, will come next. (Yes, QtWebKit will be a downstream of WebKitGTK+... it will work out fine. ;) So once that is ready, we can change our upstream for QtWebKit from the Qt project to this new project, and then we don't have to get rid of KDE applications that haven't ported to QtWebEngine. I think this can happen for Fedora 26, and then we can start doing major QtWebKit version updates to all supported Fedoras >= F26 the same way we are already handling WebKitGTK+ updates. The catch is I am not a Qt or KDE developer and so am not motivated to work on this, so someone from that community will have to step up to handle the switch, plus handle future QtWebKit updates. Note: new upstream is https://github.com/annulen/webkit/. First release is expected in 3-4 weeks. Konstantin, the developer, says it's almost ready now except for problems with QML applications that he wants to fix before releasing. Michael P.S. FWIW I agree with retiring gstreamer-0.10 and its dependencies. Old insecure libs will stay around forever unless we set a deadline for dependencies to be ported. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
