Both directly in autotools/webkit.m4 and indirectly through libsoup there's already a dependency on >= 2.21.3. Regarding stable versions, that's a dependency on glib >= 2.22. glib 2.22 was released together with gtk+ 2.18 in GNOME 2.28. Although using older gtk+ versions with glib >= 2.22 should theoretically work, serious use cases are unlikely. And it would be outside of what people usually test and use. This change not only allows getting rid of a bunch of #ifdef's and one TODO, it also documents for future changes that there's no need for comptibility with older versions.
Created attachment 52533 [details] Bump the GTK+ dependency to 2.18.
There's many embedded companies using old GTK+ versions with quite recent glib versions, and their use cases are very much "serious".
(In reply to comment #2) > There's many embedded companies using old GTK+ versions with quite recent glib versions, and their use cases are very much "serious". You can call me surprised. Do you have an example who and why does this?
(In reply to comment #3) > (In reply to comment #2) > > There's many embedded companies using old GTK+ versions with quite recent glib versions, and their use cases are very much "serious". > > You can call me surprised. Do you have an example who and why does this? Nokia with maemo. They don't upgrade because they make changes to GTK+ that are difficult and expensive to port over.
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > There's many embedded companies using old GTK+ versions with quite recent glib versions, and their use cases are very much "serious". > > > > You can call me surprised. Do you have an example who and why does this? > > Nokia with maemo. They don't upgrade because they make changes to GTK+ that are difficult and expensive to port over. Maemos glib is too old for current WebKitGTK+, but I get your general point (and should have thought of Maemo myself in the first place).