epiphany-extensions requires epiphany. Unfortunately currently stable epiphany requires xulrunner 1.9 but epiphany-extensions -- xulrunner 1.8. It's worth mentioning that xulrunner is a one of the largest packages and compiles quite a while... Reproducible: Always
This is gonna sound harsh, but learn to unmask.
(In reply to comment #1) > This is gonna sound harsh, but learn to unmask. Yes. And No. 1. I assume than the maintainers have some reasons to keep some packages keyworded. If not -- there is no sense in dividing packages into stable and unstable branches. 2. IMHO epiphany and epiphany-extensions are tightly releated and those ebuilds should be developed (and unmasked) symultanously.
hum, all my excuses, it appears epiphany-extensions had its xulrunner dependency unversioned. It even seems to be my fault :p
and fixed. Thanks for reporting and sorry for assuming you were mixing arch and ~arch keywords.
(In reply to comment #4) > and fixed. Thanks for reporting and sorry for assuming you were mixing arch and > ~arch keywords. The problem still exists! Current stable ports are: =www-client/epiphany-2.22.3-r2 (requires xulrunner-1.9) =www-client/epiphany-extensions-2.22.2 (requires xulrunner-1.8) BTW: epiphany extensions-2.22.2 experiences problems with the SSL/TLS. epiphany-extensions-2.22.2-r10 (keyworded) works better (but requires xulrunner-1.8 too!).
The ebuild should have this header: # $Header: /var/cvsroot/gentoo-x86/www-client/epiphany-extensions/epiphany-extensions-2.22.2.ebuild,v 1.8 2009/03/04 22:49:39 eva Exp $ if not, please sync.
(In reply to comment #6) > The ebuild should have this header: > > # $Header: > /var/cvsroot/gentoo-x86/www-client/epiphany-extensions/epiphany-extensions-2.22.2.ebuild,v > 1.8 2009/03/04 22:49:39 eva Exp $ > > if not, please sync. # Copyright 1999-2009 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/www-client/epiphany-extensions/epiphany-extensions-2.22.2.ebuild,v 1.8 2009/03/04 22:49:39 eva Exp $ inherit autotools eutils gnome2 python versionator MY_MAJORV=$(get_version_component_range 1-2) DESCRIPTION="Extensions for the Epiphany web browser" HOMEPAGE="http://www.gnome.org/projects/epiphany/extensions.html" LICENSE="GPL-2" SLOT="0" KEYWORDS="alpha amd64 hppa ia64 ppc sparc x86" IUSE="dbus examples pcre python xulrunner" RDEPEND=">=www-client/epiphany-${MY_MAJORV} app-text/opensp >=dev-libs/glib-2.15.5 >=gnome-base/gconf-2.0 >=dev-libs/libxml2-2.6 >=x11-libs/gtk+-2.11.6 >=gnome-base/libglade-2 xulrunner? ( =net-libs/xulrunner-1.8* )
so epiphany-extensions is good. From what I read, epiphany-2.22.3-r2 also depends on xulrunner-1.8 so this issue is fixed right ? if not please show us some emerge -pv epiphany --tree
(In reply to comment #8) > so epiphany-extensions is good. From what I read, epiphany-2.22.3-r2 also > depends on xulrunner-1.8 so this issue is fixed right ? > > if not please show us some emerge -pv epiphany --tree # Copyright 1999-2009 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/www-client/epiphany/epiphany-2.22.3-r2.ebuild,v 1.6 2009/02/26 17:31:07 ranger Exp $ inherit gnome2 eutils multilib DESCRIPTION="GNOME webbrowser based on the mozilla rendering engine" HOMEPAGE="http://www.gnome.org/projects/epiphany/" LICENSE="GPL-2" SLOT="0" KEYWORDS="alpha amd64 hppa ia64 ppc ppc64 sparc x86 ~x86-fbsd" IUSE="avahi doc networkmanager python spell xulrunner" # This release should work with xulrunner 1.9, but this revision is a # stable candidate, so stick with 1.8 here. # xulrunner-1.9 can be achieved via --with-engine=xulrunner, while # --with-engine=mozilla goes with 1.8 RDEPEND=">=dev-libs/glib-2.16.0 >=x11-libs/gtk+-2.12.0 >=dev-libs/libxml2-2.6.12 >=dev-libs/libxslt-1.1.7 >=gnome-base/libglade-2.3.1 >=gnome-base/libgnome-2.14 >=gnome-base/libgnomeui-2.14 >=gnome-base/gnome-desktop-2.9.91 >=x11-libs/startup-notification-0.5 >=x11-libs/libnotify-0.4 >=dev-libs/dbus-glib-0.71 >=gnome-base/gconf-2 >=app-text/iso-codes-0.35 avahi? ( >=net-dns/avahi-0.6.22 ) networkmanager? ( net-misc/networkmanager ) !xulrunner? ( =www-client/mozilla-firefox-2* ) xulrunner? ( =net-libs/xulrunner-1.8* ) python? ( >=dev-lang/python-2.3 >=dev-python/pygtk-2.7.1 >=dev-python/gnome-python-2.6 ) spell? ( app-text/enchant ) x11-themes/gnome-icon-theme" DEPEND="${RDEPEND} app-text/scrollkeeper >=dev-util/pkgconfig-0.9 >=dev-util/intltool-0.35 >=app-text/gnome-doc-utils-0.3.2 doc? ( >=dev-util/gtk-doc-1 )" DOCS="AUTHORS ChangeLog* HACKING MAINTAINERS NEWS README TODO" pkg_setup() { G2CONF="${G2CONF} --disable-scrollkeeper --with-engine=mozilla --enable-certificate-manager --with-distributor-name=Gentoo $(use_enable avahi zeroconf) $(use_enable networkmanager network-manager) $(use_enable spell spell-checker) $(use_enable python)" if use xulrunner; then G2CONF="${G2CONF} --with-gecko=xulrunner" else G2CONF="${G2CONF} --with-gecko=firefox" fi } The problem is that I'm using a firefox-bin so I have the USE=xulrunner global flag set (that results in using xulrunner 1.9). Mixing firefox and firefox-bin is IMHO not a smat idea...
ok I don't get what you're saying anymore. firefox-bin has it's own deps, firefox-2 (source) is an optional dep of epiphany is not using xulrunner. epiphany and epiphany-extensions now have a consistent requirement or xulrunner 1.8 at your keyword level of visibility so what is the problem ?
Mind that: # This release should work with xulrunner 1.9, but this revision is a # stable candidate, so stick with 1.8 here. # xulrunner-1.9 can be achieved via --with-engine=xulrunner, while # --with-engine=mozilla goes with 1.8 and that: if use xulrunner; then G2CONF="${G2CONF} --with-gecko=xulrunner" else G2CONF="${G2CONF} --with-gecko=firefox" fi Epiphany can depend on firefox or xulrunner. Because I have a firefox-bin it's desired that epiphany depends on xulrunner (in the other case I would have firefox and firefox-bin which is impossible -- they block each other). So I have the "xulrunner" USE flag set. That means: epiphany builds again xulrunner-1.9. As a result I hava a xulrunner-1.9 as a requisite...
Oups! I have confused engine and gecko. Sorry! My fault.
You mean you want a epiphany that builds against xulrunner-1.9 ? if so, you want to look at the -r10 variations of the ebuild, xulrunner has been stable for not so long and we didn't ask for stabilization stabilization of gnome-2.22 components because they were not really all migrated in time or well so it was better to wait for 2.24 which is on the way to stable.
Let me clarify: [19:50 athena] epiphany> grep net-libs/xulrunner epiphany-2.22.3-r* epiphany-2.22.3-r11.ebuild: =net-libs/xulrunner-1.9* epiphany-2.22.3-r12.ebuild: =net-libs/xulrunner-1.9* epiphany-2.22.3-r1.ebuild: xulrunner? ( =net-libs/xulrunner-1.8* ) epiphany-2.22.3-r2.ebuild: xulrunner? ( =net-libs/xulrunner-1.8* ) Note: -r1 and -r2 against 1.8, -r11 and -r12 against 1.9 [19:51 athena] epiphany-extensions> grep net-libs/xulrunner epiphany-extensions-2.22.2* epiphany-extensions-2.22.2.ebuild: xulrunner? ( =net-libs/xulrunner-1.8* ) epiphany-extensions-2.22.2-r10.ebuild: =net-libs/xulrunner-1.9* Note: 2.22.2 against 1.8, -r10 against 1.9. This is consistent. The -r < 10 is against 1.8, -r > 10 is against 1.9. The xulrunner deps of the 2 must match.