-
-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get rid of webkitgtk24 #18312
Comments
Packages that need the old api should probably be just migrated to webkit 2.10 |
(cherry picked from commit 2ef4e9e) Signed-off-by: Domen Kožar <domen@dev.si>
Is |
@gebner No. There's no one "old api". We've covered this all in #17308 but essentially there were 4 API deprecations resulting in 4 distinct branches: 2.4, 2.6, 2.10 & 2.12. In fact, upstream doesn't support 2.4, 2.6 & 2.10 and considers 2.12 the stable branch. Worse, the 2.10 branch had consecutive security issues and ended up getting stricken off the change-logs as if it was some development unstable branch... |
I was hoping we could remove webkitgtk for gnome 3.22, but it turns out, it's still needed... |
More uses:
|
How are these projects still using such an old dependency? |
I think it's mainly upstream not adding support; I've got no idea why that goes so slowly. As a consequence, e.g. the latest Debian (unstable) still defaults to 2.4.x, and even same in Arch. |
List of packages still depending on webkitgtk24x (checked if fixed or removed):
|
I vote to remove the support and mark packages that have a hard dependency on it as broken. I think emacs xwidget support is a bit of a gimmick so I for one wouldn't consider it a great loss if it had to be disabled. |
emacs 25.2 upgrades wxwidgets to use a recent webkitgtk. |
Marking |
There are even more packages on 2.4, since
|
That. In fact, people over at freenode#emacs were horrified, when I told them the other day, that the xwidget browser thing had javascript support turned on. |
It seems unlikely, for all the mentioned packages to be fixed in time for the upcoming stable. I'd support marking webkitgtk24 as broken. I've been running a patch to do so for 2 master rebuilds now. The
|
With @joachifm's PR merged, it isn't removed but it is disabled by default. |
Let's close. Webkit 2.4 is unusable unless you explicitly disable security check; that seems fair, and it's up to packages using this to choose (update). |
It can not be built in parallel so it takes 6+ hours to build, sometimes even 9h.
cc @lethalman @DamienCassou
The text was updated successfully, but these errors were encountered: