On Apr 11, 2013, at 9:59 PM, Robert Schroll wrote:

> We're now using the context_menu signal of WebViews, which seems to have been 
> introduced in 1.10.  Also, when I do attempt to compile, I get stuck on 
> WebKit warnings:
> 
> WebKit-3.0.metadata:6.9-6.34: warning: metadata never used
> WebView.entering_fullscreen#signal name="entering_fullscreen_signal"
>         ^^^^^^^^^^^^^^^^^^^^^^^^^^
> WebKit-3.0.metadata:7.9-7.33: warning: metadata never used
> WebView.leaving_fullscreen#signal name="leaving_fullscreen_signal"
>         ^^^^^^^^^^^^^^^^^^^^^^^^^
> Compilation failed: 0 error(s), 2 warning(s)
> make[2]: *** [src/.geary.stamp] Error 1
> 
> If I remove those lines from the metadata file, I get error messages on 
> missing WebKit symbols.

Forgot about that one.  The reason we added the WebKitGTK3 gir file in to our 
repo in the first place was so we could work on Precise, which didn't have the 
gir file, and on Quantal and Raring, which had a deprecation warning regarding 
the old context menu API.

> ppa:laney/webkit-backports-2 has webkit 1.10 for 12.04.  But with this, 
> neither Synaptic nor aptitude can come up with a solution for upgrading 
> webkit without removing a bunch of other packages.  This has me worried.

That would worry me too.  Maybe consider building from source?  I've 
successfully built WebKitGTK3 before, if you want to try that it's not as bad 
as it sounds.  You can disable most of the features at configure time since 
Geary only uses a small feature set.  I stupidly didn't write down which 
options I used last time I built it.  (If you go this route, please document 
this part somewhere.)  You can probably get away with grabbing the gir file 
from Quantal if you don't want to enable gobject-introspection and the 
dependencies that requires.

 - Eric

_______________________________________________
Geary mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/geary

Reply via email to