Epiphany 1.6.1 needs some care. :)
Created attachment 55921 [details] Epiphany-1.6.1.ebuild
Created attachment 55922 [details] include fixes for epiphany-1.6.1-ebuild
Created attachment 55923 [details] epiphany-extensions-1.6.1.ebuild
Created attachment 55924 [details] include fixes for epiphany-extensions-1.6.1-ebuild
I might add that this release fixes a very annoying bug, (clicking on links to f.ex pdf files just downloads the file, and doesn't open it). So maybey this should also block bug #84701
btw, the above mentioned bug is http://bugzilla.gnome.org/show_bug.cgi?id=171197 I agree with the above comment; it significantly impacts usability. 1.6.2 ebuilds on the way.
Created attachment 56677 [details] epiphany-1.6.2.ebuild
Created attachment 56678 [details] epiphany-1.6.2-fix_includes.patch
Created attachment 56679 [details] epiphany-extensions-1.6.2.ebuild
Created attachment 56680 [details] epiphany-extensions-1.6.2-fix_includes.patch I did not submit my local portage ebuilds for ephy 1.6.2. The Bugzilla-Report is not valid for 1.6.2 anymore. Opening downloads works as expected.
Created attachment 56939 [details] epiphany-1.6.2.ebuild Changes: 1. dbus support works 2. need to be able to choose gecko provider: mozilla or firefox
Created attachment 56940 [details] epiphany-extensions-1.6.2.ebuild Changes: 1. dbus support (net-monitor extension) 2. dashboard, tab-states extensions
this should be assigned to gnome
Can sothing finally be done to compile against firefox, the bug concerning the hypotetical possibility to compile epiphany against is fixed according to firefox ebuild changelog, but in fact it doesn't work.. Can somthing finally be done for that ? That would also allow to enable more extensions, like the find bar ..
Ed: There are extensions, which will not make it into ebuild until epiphany 1.8 is released. E.g. adblock is not stable and crashes epiphany on exit. This is not an option. It should either be made optional or removed at all. Anyway, why are we submitting ebuilds for epiphany at all? The currently provided firefox-ebuild renders firefox into a "theoretically possible" installation and until this has not been fixed, see also http://bugs.gentoo.org/show_bug.cgi?id=89364, it does not make any sense. I thought Brad has gracefully "included" the mozilla-headers into the ebuild. Well, if he had just taken my ebuild, it'd now, but no, he replaced configure by econf .. great work. Ed, save your energie please, as long as the firefox-ebuild has not been fixed, there is no need for updated epiphany ebuilds anymore. I thing Brad is an expert on this and will certainly fix this all. *sigh* Maybe you just wonder, why I'm writing this. Just because I'm sick of stupid changes!
So no ebuild for 1.6.3 :-(
Do you see any reasons, why? See also http://bugs.gentoo.org/show_bug.cgi?id=89364
Ebuilds for epiphany and epiphany-extensions 1.6.4 exist now in the tree, including the suggestions presented in this bug. Thank you all for your help. For future reference, please note that it'd be nice if only the diffs against our current ebuilds are posted, although I guess this is more of a personal preference :).
