Here's a new set of ebuilds for the epiphany extensions. They depend on >=epiphany-1.2.1 and I've created a separate ebuild for each extension so you don't have to install the whole lot. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 28511 [details] epiphany extensions 0.8.1 ebuilds
attach plaintext please dunno if its worth the trouble to split them up btw.
Created attachment 28555 [details] certificate viewer ebuild
Created attachment 28556 [details] error viewer ebuild
Created attachment 28557 [details] mouse gestures ebuild
Created attachment 28558 [details] popup blocker ebuild
Created attachment 28559 [details] tabs menu ebuild
plaintext attached as requested. As for splitting them up, different extensions can feasably have different dependancys, i.e. there is a dashboard extension that I have not included an ebuild for due to the lack of an ebuild for dashboard. There may also be various new extensions from third parties in the future. That said, you're the boss, so please advise.
about the ebuilds : they should probably use the gnome2 eclass & use G2CONF to pass the extension(s) to be built. I miss the usual docs like README etc. About the split-up, i do not see any dep besides epiphany here. We could always split them up at a later time. 3rd party extensions probably won't be part of this package.
Created attachment 28568 [details] epiphany extensions ebuild Rewritten as a single ebuild. This ebuild builds all the extensions other than dashboard as this depends on dashboad which is not in the portage tree. I've used the gnome2 eclass this time and have included the relevent docs.
*** Bug 30387 has been marked as a duplicate of this bug. ***
*** Bug 47633 has been marked as a duplicate of this bug. ***
I've tested this ebuild on amd64 and it compiles and runs perfectly. Please add "~amd64" to the KEYWORDS. Is there anything holding this back from being committed?
Desperately waiting for this package to be in my portage tree...any idea if anything is holding it up?
please use the attached patch to make gestures work with the right button, not the frigging mouse wheel ;)
Created attachment 37472 [details] gestures use the right button.
to add the patch to the ebuild: inherit base PATCHES="${FILESDIR}/epiphany-extensions-1.0-rightbutton.patch" Thanks.
Created attachment 45792 [details] ebuild and patches necessary for the version 1.4.3 Here is a new version of the ebuild tweaked for the version 1.4.3 of epiphany-extensions.
As the author of error-viewer, I'll just mention that Error Viewer really only shines if built against OpenSP, since it can do local HTML validation (word-for-word equivalent to w3.org's). Debian's epiphany-extensions package, for instance, depends on libosp4, sgml-data and w3c-dtd-xhtml; and it has a build-dep of libosp-dev. Gentoo almost certainly has equivalent packages. If OpenSP is installed, Error Viewer will rock.
Created attachment 49569 [details] epiphany-extensions-1.4.4.ebuild A new version, also there are some small corrections (COPYING in DOC, wrong header, different patch name, different depend-version) Did this because I hoped I could use this stuff for beagle...well, it didn't worked out ;) kai
Created attachment 49570 [details] 99epiphany-extensions
Created attachment 49571 [details] epiphany-extensions-1.4.4-path.patch
I think .diff would be the better suffix, does it? Worked well on my ~x86-system. foser, spider: is it possible to put this in portage?
Created attachment 51393 [details] epiphany-extensions-1.4.5.ebuild There's a new upstream version, ebuild attached. Regarding the last ebuild posted: 1) the patch to configure is unnecessary; set USE_DESTDIR="1" instead. 2) I don't see the need for the env.d script; epiphany finds these modules as long as they're in the extensiondir. WFM w/o it.
I've added 1.4.5 to CVS, thanks for your submissions.
