When using both USE-variables "firefox" and "xulrunner" (for additional
"seamonkey" its even a next step) dev-haskell/gtk2hs builds/depends on firefox
and xulrunner. When xulrunner is set, only xulrunner should be used
for example see gnome-python-extras:
xulrunner? ( =net-libs/xulrunner-1.8* )
!xulrunner? ( firefox? ( =www-client/mozilla-firefox-2* ) )
!xulrunner? ( !firefox? ( seamonkey? ( =www-client/seamonkey-1* ) ) )
Reproducible: Always
Steps to Reproduce:
1. USE="firefox xulrunner" emerge -pv =gtk2hs-0.9.12.1
2.
3.
Actual Results:
www-client/mozilla-firefox-xxx
net-libs/xulrunner
dev-haskell/gtk2hs
Expected Results:
net-libs/xulrunner
dev-haskell/gtk2hs
expected ebuild: see
/usr/portage/dev-python/gnome-python-extras/gnome-python-extras-2.19.1-r1.ebuild
This does indeed not match with use flag preference in other ebuilds, afaik.
@mozilla team: While I think that the gtk2hs ebuild should be changed for
consistency reasons, the transition from FF2 to 3 will not be trivial for Joe
User and we cannot start early enough (the Mozilla foundation supports FF2 till
December iirc) to think about changing the tree, including a tracker bug and a
prepared announcement, when FF3 goes stable.
