Am Montag, den 20.10.2014, 11:25 +0200 schrieb Fabian Greffrath: > In the current Debian package, the plugin is built, but not installed. > Please add the /usr/lib/mozilla/plugins path to the appropriate > debian/*.install files.
I have tested the plugin locally and it works great with Epiphany. If we decide to ship it in Debian (I mean, should we? This plugin comes a bit late, as NPAPI is widely considered mostly dead nowadays.), should we ship it in a separate package, like e.g. totem did, or stuff it into the main package? I don't think it will pull in any GNOME-only dependencies: $ objdump -x ./debian/install/evince/usr/lib/mozilla/plugins/libevbrowserplugin.so | grep NEEDED NEEDED libevview3.so.3 NEEDED libevdocument3.so.4 NEEDED libgmodule-2.0.so.0 NEEDED libz.so.1 NEEDED libgtk-3.so.0 NEEDED libgdk-3.so.0 NEEDED libpangocairo-1.0.so.0 NEEDED libpango-1.0.so.0 NEEDED libatk-1.0.so.0 NEEDED libcairo-gobject.so.2 NEEDED libcairo.so.2 NEEDED libgdk_pixbuf-2.0.so.0 NEEDED libgthread-2.0.so.0 NEEDED libgio-2.0.so.0 NEEDED libgobject-2.0.so.0 NEEDED libglib-2.0.so.0 NEEDED libstdc++.so.6 NEEDED libm.so.6 NEEDED libc.so.6 NEEDED libgcc_s.so.1 - Fabian
signature.asc
Description: This is a digitally signed message part
