On a new system I've emerged www-client/epiphany-2.22.3-r10 (ACCEPT_KEYWORDS=~amd64). It pulled in and built successfully against xulrunner-1.9-r2. When I then wanted to emerge epiphany-extensions-2.22.2 this build failed due to missing xulrunner-1.8.1.15 on the clean system. The epiphany-2.22.3-r10.ebuild passes "--with-gecko=libxul-embedding" to configure. The same option would work for epiphany-extensions. Why should I build epiphany and its extensions against two different geckos? Reproducible: Always
Created attachment 160180 [details] emerge --info
Created attachment 160181 [details, diff] patch for an epiphany-extensions-2.22.2-r10.ebuild This works, I am however not absolutely sure about the version check of epiphany
This bug breaks the Page Info extension (View->Page Information): ** (epiphany:4426): CRITICAL **: general_info_page_fill: assertion `props != NULL' failed The page-info dialog comes up blank, and epiphany segs when it is closed: Program received signal SIGSEGV, Segmentation fault. mozilla_free_embed_page_info (info=0xc231530) at mozilla-helpers.cpp:1166 1166 g_free (props->content_type); This is because between xulrunner-1.8 and xulrunner-1.9 the IID of nsIDOMNSDocument has changed, so if epiphany-extensions is built against xulrunner-1.8 it will fail to QI the nsIDOMNSDocument out of nsIDOMDocument: http://newsgroups.cryer.info/mozilla/dev.tech.dom/200802/0802041033.html
Confirm the patched ebuild builds/links against the correct xulrunner.
