If you are trying to update or install an AUR package and your system suddenly starts a massive, hours-long compilation of webkit2gtk, stop the process. The Problem: Naming Confusion Previously, the official repositories contained two packages:
webkit2gtk-4.1(extra repo) (The modern version)webkit2gtk(AUR now) (The legacy 2.5 version)
The legacy version (webkit2gtk) has been moved to the AUR. Now, when an older AUR package lists webkit2gtk as a dependency, your AUR helper (like yay or paru) finds it in the AUR and tries to build it from source. This is rarely what you want.
This is insane? yes do not do that please!. remove that dangerous outdated thing and use the version from repo https://archlinux.org/packages/extra/x86_64/webkit2gtk-4.1/ if you can.
If you have something that really depends on the 2.5 version there are a bin version on the AUR:
webkit2gtk-bin (precompiled) —> https://aur.archlinux.org/packages/webkit2gtk-bin
And you can also find this thing:
A Dummy package redirecting webkit2gtk to webkit2gtk-4.1 so you can build AURs that has webkit2gtk still in PKGBUILD but may would also simply work with 4.1 version of it.
and only to complete… use yay -Qi webkit2gtk to check what is depending on it..
Advice for AUR Users
If you encounter a package that still forces the legacy webkit2gtk from source, please leave a comment on that package’s AUR page. Suggest that the maintainer updates the PKGBUILD to support webkit2gtk-4.1 or at least points users toward the -bin alternative.
Or link to that here so someone with an account can hint on the AUR page.