Bug 238932 - [GTK4] Revisit required vs. optional dependencies (especially libwpe, wpebackend-fdo, and libepoxy)
Summary: [GTK4] Revisit required vs. optional dependencies (especially libwpe, wpeback...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
Depends on:
Blocks: GTK4
  Show dependency treegraph
Reported: 2022-04-07 07:09 PDT by Michael Catanzaro
Modified: 2022-06-15 13:51 PDT (History)
5 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Catanzaro 2022-04-07 07:09:02 PDT
For GTK 4, we should make sure that certain dependencies are required from the start. Most importantly, we should require libwpe and wpebackend-fdo to ensure nobody is still using -DUSE_WPE_RENDERER=OFF.

I think we should also require libepoxy, and also libsoup 3 (if that's not required already).
Comment 1 Carlos Garcia Campos 2022-04-08 00:57:46 PDT
Yes, the idea is to make all deps that are optional because of the deps policy mandatory for gtk4 build (soup3 and wpe for sure)
Comment 2 Michael Catanzaro 2022-04-08 07:58:23 PDT
Other libs we could possibly require: libmanette (doesn't exist in RHEL, but probably should), libsecret, enchant, libhyphen, libtasn1, openjpeg, woff2, lcms2

Stuff we probably (?) don't want to require: jpegxl (experimental), libnotify (deprecated and bad), libgcrypt (bad, could be replaced with OpenSSL WebCrypto backend), avif (experimental), thunder