the trouble with mozilla branding is based around binary packages ... we have a USE flag just for this (bindist) as for building on user's systems, we're not redistributing binaries, so let users get the branding with their customizations
app-office/mozilla-sunbird mail-client/mozilla-thunderbird www-client/mozilla-firefox have all mozbranding replaced by bindist and enabled the branding by default. For firefox i just modified the latest ebuild, which should be stable wrt bug 165555. So it's up to you to close this bug or not, i'll close it when i can clean up the oldish firefox ebuilds(which i'm waiting for the arches to stabilize the newer)
mostly :) the default user emerging firefox will now get a branded version (yeah!) so as to be clear, does USE=bindist give a branded firefox ?
(In reply to comment #2) Yep.
then i've got nothing else thanks a ton