portage's mozilla-firefox provides firefox-icon.png with the mozbranding useflag. x11-themes/garton-0.5 includes mozilla-firefox.svg, but doesn't show unless it's copied/symlinked to firefox-icon.svg. also, something could be done for firefox w/o branding. perhaps the ebuild could symlink gnome-globe.svg to firefox-icon-unbranded.svg. epiphany.svg is another possibility but could lead to confusion when both iceweasel and epiphany are installed.
(In reply to comment #0) What does this have to do with mozilla ebuilds? Messing with them just because some third-party icon set doesn't work properly and needs symlinks makes little to no sense.
(In reply to comment #1) > What does this have to do with mozilla ebuilds? I've seen a few third-party icon sets provide mozilla-firefox.svg but not firefox-icon.svg. Google turns up many references to both mozilla-firefox.png and firefox-icon.png. It seems other linux distributions or Mozilla releases provide mozilla-firefox.png instead of firefox-icon.png. The mozilla ebuilds are fine. gartoon-0.5-r1.ebuild needs two dosym lines added.
Created attachment 104024 [details, diff] gartoon-0.5-r1.ebuild.patch symlink icons for firefox-icon{,-unbranded}
(In reply to comment #3) > Created an attachment (id=104024) [edit] > gartoon-0.5-r1.ebuild.patch > > symlink icons for firefox-icon{,-unbranded} > Done. Thanks.
