Concerning Gnome Ebuilds....Several ebuilds (Yelp and epiphany in particular) demand Mozilla-1.7.x installed only by Gentoo rather than to check the system. Worse is that these ebuilds will automatically install mozilla-1.7.x on top of the Firefox-1.5.x, Mozilla-1.8b, or the Seamonkey-1.0.1 programs that I compiled from Mozilla's source tarballs and installed on my system. Installing moz-1.7.x messes up anything I had installed before. Options listed in packages.masked or packages.provided for keeping mozilla-1.7.x off the system make no difference. Please fix the ebuilds to start checking the system first for either Firefox, mozilla, or seamonkey sources (pkg-config files will show the way) and quit automatically installing the old mozilla-1.7.x packages on the system. BTW, Firefox and Seamonkey also carry the latest gecko engines, and I have fooled the system more than once to compile with Seamonkey...epiphany and yelp work perfectly with seamonkey and/or firefox. I marked this as a blocker because the packages don't emerge, or my browser with plugins gets messed up everytime moz-1.7.x is installed over my newer seamonkey-1.0.1. Speaking of which, why isn't seamonkey-1.0.1 sources in portage by now?
Both yelp and epiphany can use can use either mozilla or firefox (if USE=firefox is set). If you want something else (seamonkey/gecko-sdk), then submit a patch after you have tested that it works. And - one ebuild, one bug. Marking WORKSFORME, file new bugs with patches for each of the ebuilds, and definitely don't mark them as blockers.
This may work for you, but it is a show stopper for me everytime I try to update anything in gnome. That is why I marked it as a blocker. Please see the following response about this bug being reported to gnome.org: Comment #3 from Don Scorgie (Yelp developer, points: 14) 2006-05-31 09:55 UTC [reply] Hi, As has been pointed out, Seamonkey is available as a back-end. This has been the case since yelp 2.12 (although it appears that 2.12.x pretended it didn't in the configure flags. I don't know why, but it could be build with seamonkey). Since 2.13, yelp is using epiphany's script to handle which mozilla to use, which does include seamonkey. ============== Please fix the ebuild & quit requiring Mozilla-1.7.x in every case, especially when a more advanced browser version like mozilla, firefox, and seamonkey are already installed on a system.
We don't want summary bugs for unspecified ebuilds; I've already told you what to do.
Oh, as far as me making the patch to the ebuild & portage system, it isn't going to happen.....especially for something that is already in the source tarball and should just be reflected in the ebuild. You guys are the maintainers of these ebuilds, not me. The passing of the buck gets you guys no points. If this ebuild was fixed/created properly the first time, there would have been no bug to report. Sorry for the harshness, but maybe you guys might understand my frustration if your machine was brought to a stop everytime you upgraded like mine was (Final straw was when my machine was rendered inoperable for a month due to an ebuild that didn't work properly).
So... - this is a distribution maintainer by volunteer unpaid developers - if you are requesting something, you'd better change your attitude, the above won't get you too far. - I've explained twice that we don't want mass bugs for unspecified number of ebuilds, and told you to file separate bugs for each of them. - the ebuilds work just fine here, you've submitted zero useful information wrt your problem w/ mozilla. Also, you probably missed firefox use flag altogether, better do a bit of research before you start moaning. - sure, we should have accounted for your Seamonkey support since Gnome 1.4 times preferably, never mind that Seamonkey ebuild has been in portage since end of February only. Closing.