After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 735299 - WebKit2-4.0 support
WebKit2-4.0 support
Status: RESOLVED FIXED
Product: gitg
Classification: Applications
Component: gitg
git master
Other Linux
: Normal major
: ---
Assigned To: gitg-maint
gitg-maint
Depends on:
Blocks:
 
 
Reported: 2014-08-23 21:17 UTC by Dominique Leuenberger
Modified: 2015-08-08 08:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dominique Leuenberger 2014-08-23 21:17:17 UTC 
With 
https://git.gnome.org/browse/gitg/commit/?id=a1cdc51c6613af994b8517531fca06f435d43e28

gitg allows to be configured to be built against webkit2gtk-3.0 or webkit2gtk-4.0.

There is an issue though with the released tarballs (tested 3.13.91): the file Gitg-1.0.gir is distributed with a 'fixed' reference to a WebKit variant as per the version used during make dist:

In 3.13.91 for example, this file contains
  <include name="WebKit2" version="3.0"/>

which in turn causes build issues when building against webkit2gtk-4.0 (possibly masked/hidden away, in case webkit2gtk-3.0 is also installed)
Comment 1 jessevdk@gmail.com 2014-08-25 10:57:25 UTC 
I wonder what the proper solution for this is. I guess we should regenerate the gir each time, but it's not exactly standard.
Comment 2 jessevdk@gmail.com 2015-08-08 08:55:46 UTC 
This problem has been fixed in the unstable development version. The fix will be available in the next major software release. You may need to upgrade your Linux distribution to obtain that newer version.