Many applications embed the Gecko engine in order to show HTML, and most of them depend on Mozilla. However, Firefox is now also able to be used as an SDK, and this situation requires ebuild maintainers to adapt every single ebuild to support firefox. This is done in a rather inconsistent manner: sometimes the firefox USE flag is used, and sometimes the ebuild just depends on either Mozilla or Firefox. I suggest that both Mozilla and Firefox would provide virtual/gecko, and all other ebuilds will depend on it. Also, Gecko should be provided alone, in case the user doesn't want any of the Mozilla browsers (I, for example, use Epiphany), and should be the default option for satisfying the virtual dependency.
(In reply to comment #0) I vote for this virtual/gecko solution, too. Or is there anything in the way? We should do this.
Too many virtuals killed a kitten. :P Seriously, mozilla and gecko-sdk are about to be removed from the tree, no point in creating an artificial virtual for FF/Seamonkey when those two things are often not mutually compatible replacement so the virtual couldn't be used anyway (see Bug 137665 for the porting-related issues). WONTFIX.
