It can not be built in parallel so it takes 6+ hours to build, sometimes even 9h.
$ git grep webkitgtk24
pkgs/applications/editors/emacs-25/default.nix:, withXwidgets ? false, webkitgtk24x ? null, wrapGAppsHook ? null, glib_networking ? null
pkgs/applications/editors/emacs-25/default.nix:assert withXwidgets -> withGTK3 && webkitgtk24x != null;
pkgs/applications/editors/emacs-25/default.nix: ++ stdenv.lib.optionals withXwidgets [webkitgtk24x wrapGAppsHook glib_networking];
pkgs/desktops/gnome-3/3.20/default.nix: inherit (pkgs) glib gtk2 webkitgtk24x webkitgtk212x gtk3 gtkmm3 libcanberra;
pkgs/desktops/gnome-3/3.20/default.nix: # webkitgtk = webkitgtk24x;
pkgs/desktops/gnome-3/3.20/default.nix: webkitgtk = webkitgtk24x;
pkgs/desktops/gnome-3/3.20/default.nix: webkitgtk = webkitgtk24x;
pkgs/desktops/gnome-3/3.20/default.nix: webkitgtk = webkitgtk24x;
pkgs/desktops/gnome-3/3.20/default.nix: webkitgtk = webkitgtk24x;
pkgs/development/haskell-modules/configuration-common.nix: webkitgtk3 = super.webkitgtk3.override { webkit = pkgs.webkitgtk24x; };
pkgs/development/haskell-modules/configuration-common.nix: webkitgtk3-javascriptcore = super.webkitgtk3-javascriptcore.override { webkit = pkgs.webkitgtk24x; };
pkgs/development/haskell-modules/configuration-common.nix: websnap = super.websnap.override { webkit = pkgs.webkitgtk24x; };
pkgs/tools/networking/mu/default.nix:, gtk3, webkitgtk24x, libsoup, icu }:
pkgs/tools/networking/mu/default.nix: gtk3 webkitgtk24x ];
pkgs/top-level/all-packages.nix: webkitgtk24x = callPackage ../development/libraries/webkitgtk/2.4.nix {
pkgs/top-level/all-packages.nix: webkitgtk2 = webkitgtk24x.override {
pkgs/top-level/all-packages.nix: webkitgtk = webkitgtk24x;
pkgs/top-level/all-packages.nix: webkitgtk = webkitgtk24x;
cc @lethalman @DamienCassou
@gebner could we bump webkitgtk version for mu? See ad41b8fa197cbab795ea01ca7becf6548391ef5c
Packages that need the old api should probably be just migrated to webkit 2.10
Is webkitgtk210x
the new version with the old API? I just tried to build mu against it, but apparently we don't build webkitgtk210x
on hydra. Is there a reason for hydra not building it?
@gebner No. There's no one "old api". We've covered this all in https://github.com/NixOS/nixpkgs/issues/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...
https://bugs.launchpad.net/ubuntu/+source/bijiben/+bug/1588150
For us this affects bijiben and geary :disappointed:
More uses:
git grep 'webkitgtk2[^41]'
pkgs/applications/audio/guitarix/default.nix:, webkitgtk2, wrapGAppsHook, zita-convolver, zita-resampler
pkgs/applications/audio/guitarix/default.nix: libsndfile lilv lv2 serd sord sratom webkitgtk2 zita-convolver
pkgs/applications/editors/eclipse/build-eclipse.nix:{ stdenv, makeDesktopItem, freetype, fontconfig, libX11, libXrender, zlib, jdk, glib, gtk2, libXtst, webkitgtk2, makeWrapper, ... }:
pkgs/applications/editors/eclipse/build-eclipse.nix: --prefix LD_LIBRARY_PATH : ${stdenv.lib.makeLibraryPath ([ glib gtk2 libXtst ] ++ stdenv.lib.optional (webkitgtk2 != null) webkitgtk2)} \
pkgs/applications/editors/eclipse/default.nix:, webkitgtk2 ? null # for internal web browser
pkgs/applications/networking/browsers/dwb/default.nix:{ stdenv, fetchgit, pkgconfig, makeWrapper, libsoup, webkitgtk2, gtk2, gnutls
pkgs/applications/networking/browsers/dwb/default.nix: webkitgtk2 gtk2 gnutls json_c m4 ];
pkgs/applications/networking/mailreaders/claws-mail/default.nix: ++ optional enablePluginFancy webkitgtk2;
pkgs/applications/office/osmo/default.nix:, libarchive, gtkspell2, webkitgtk2, libgringotts }:
pkgs/applications/office/osmo/default.nix: gtkspell2 webkitgtk2 libgringotts ];
pkgs/applications/video/miro/default.nix:, pythonPackages, pyrex096, ffmpeg, boost, glib, gtk2, webkitgtk2, libsoup
pkgs/applications/video/miro/default.nix: pkgconfig pyrex096 ffmpeg boost glib gtk2 webkitgtk2 libsoup
pkgs/development/haskell-modules/configuration-common.nix: webkit = super.webkit.override { webkit = pkgs.webkitgtk2; };
pkgs/top-level/all-packages.nix: webkitgtk2 = webkitgtk24x.override {
pkgs/top-level/all-packages.nix: webkit = webkitgtk2;
pkgs/top-level/all-packages.nix: webkit = webkitgtk2;
pkgs/top-level/all-packages.nix: webkit = webkitgtk2;
pkgs/top-level/all-packages.nix: webkit = webkitgtk2;
pkgs/top-level/all-packages.nix: webkitgtk = webkitgtk2;
pkgs/top-level/all-packages.nix: webkit = webkitgtk2;
pkgs/top-level/all-packages.nix: webkit = webkitgtk2;
pkgs/top-level/python-packages.nix: pkgs.libxslt pkgs.libsoup pkgs.webkitgtk2 pkgs.icu
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 webkitgtk24
itself as broken should be enough. That won't propagate to nix-env -qa
normally, but it will throw the message on evaluation.
There are even more packages on 2.4, since webkitgtk2
is derived from webkitgtk24x
:
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.
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 kde5
derivation continues to evaluate and for gnome3
I've just had to deactivate an optional package bijiben
, see
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).
Most helpful comment
With @joachifm's PR merged, it isn't _removed_ but it is disabled by default.