Setting up Epiphany to play with Seed extensions
- Magnus Therning
Since the Python extensions to Epiphany have been removed from the repository I thought it was high time to start playing with what seems to be the replacement to Python extensions: Seed extensions. The first step is of course to get a version of Epiphany that supports Seed extensions. After a few emails on the mailing list I’ve come to a recipe (I’ve done this twice now on different machines to I’m fairly confident it works). I should probably preface this by saying that I run an up-to-date Arch system, if you run something else you might need to do a bit more, or less if you’re lucky :-)
Make sure the following packages are installed ((You might need a few more packages depending on what desktop environment you use. Those were the packages I needed to add to my machine where I run Gnome and do regular non-Gnome development)):
libsoup
,libwebkit
,gnome-common
,intltool
,libffi
Clone the following Git repositories from git.gnome.org:
epiphany-extensions
,epiphany
,seed
,gobject-inspection
,gnome-js-common
,gir-repository
Decide on a
$prefix
, i.e. where you want it all installed (I use~/opt/gnome-trunk
). Then export the following environment variables:export PATH=$prefix/bin:$PATH export PKG_CONFIG_PATH=$prefix/lib/pkgconfig
Then configure, build and install everything. Use the
autogen.sh
script to create the configuration, and make sure to pass itprefix=$prefix
each time. Some of the modules need extra arguments as well. This is the order and extra arguments I used:gnome-js-common
(--disable-seed --disable-gjs
)seed
gnome-js-common
(--disable-gjs
)gobject-introspection
gir-repository
epiphany
(--enable-introspection --enable-seed
)epiphany-extensions
After that you can put your extensions in ~/.gnome2/epiphany/extensions/
. I have two instances of Epiphany installed, a stable from my distro, and the dev version I built myself. I haven’t managed to run them both side by side, but beyond that there seems to be no bad interaction between them.