The webkitgtk3 package will be removed from rawhide after Fedora 26 is branched due to the high number of unfixed security vulnerabilities. You must remove this dependency or your package will not be present in Fedora 27. Please refer to [1] for a FAQ on this matter and be advised that for some packages this may require a substantial amount of work. Note: For seed, you can just flip the configure flag to use webkit2gtk-4.0.pc [1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/AKVB363GFCHHJ5MTHGVYHYT6NLLTF5VM/
(In reply to Michael Catanzaro from comment #0) > Note: For seed, you can just flip the configure flag to use webkit2gtk-4.0.pc Actually it is not that easy as the seed needs to be updated to the newest version from git. Maybe we could convince the upstream (I will try to talk with them) to make the 4.0 release or we have to package the git snapshot.
That's one option. Alternatively we could let it die. Nothing needs it and if there's no release in years, that indicates the project is very unhealthy, regardless of activity in git. We probably don't want any applications using it anyway.
(In reply to Michael Catanzaro from comment #2) > That's one option. Alternatively we could let it die. Nothing needs it and > if there's no release in years, that indicates the project is very > unhealthy, regardless of activity in git. We probably don't want any > applications using it anyway. Yes, it the end I'm fine with dropping it. Initially I thought that something from the GNOME stack is using it, but I was wrong.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
latest Git does not compile cleanly against webkitgtk4 (it does not even include the right pkgconfig file, which makes me think it's not even a tested configuration). There are compilation errors even after fixing that, and since there are no dependents, I'm retiring it in Rawhide.
Wow you're right... I see https://git.gnome.org/browse/seed/commit/configure.ac?id=6d512b5c4d774a9853b51dae464a10cea7e3423a indeed got the pkg-config filename wrong. And seems to have attempted to build against GTK+ 4, which could never have worked. I guess that must never have been tested.
Ah, I noticed that Debian has a package and was curious how. Turns out it's not being passed to pkg-config at all, it uses AC_CHECK_LIB. So I presume it should be possible to get it working. Still, if no applications depend on it, it's not really any loss.