From: "Mark Haney" <mhaney@ercbroadband.org>
To: <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] firefox 2 on amd64
Date: Wed, 03 Jan 2007 15:11:47 -0500 [thread overview]
Message-ID: <459C0E03.3080003@ercbroadband.org> (raw)
In-Reply-To: <200701031132.14304.bss03@volumehost.net>
Boyd Stephen Smith Jr. wrote:
> On Wednesday 03 January 2007 09:49, "Mark Haney" <mhaney@ercbroadband.org>
> wrote about 'Re: [gentoo-amd64] firefox 2 on amd64':
>> Stefan Vunckx wrote:
>> Okay I compiled and installed it, it works great but does anyone else
>> see it in their menu list as 'Bon Echo'? I also see that in the title
>> bar. I haven't rebooted or regenerated my kde menu since compiling it,
>> but will doing that fix the menu?
>
> As others have mentioned, check the mozbranding USE flag.
>
> Any binaries that aren't from the pristine source (e.g. with any unapproved
> patches) that use the Mozilla Branding (i.e. the Firefox name and Icon,
> controlled in Gentoo with the mozbranding USE flag) are subject to the
> same issue that Debian saw during the "IceWeasel" debacle
>
> Personally, I deal with enough branding, so I leave the mozbranding USE
> flag off. [As a side-effect, any packages or binaries I build can be
> freely distributed under my choice of the GPL or MPL since they are not
> subject to trademark issues.]
>
Ah, now it makes sense. But since I have no intention of building
anything to be distributed or used for other than what it was designed
for, I'm okay with the branding. Most times I treat brands like I treat
my kids when they get rowdy, I mentally turn off any notice of them.
--
Ita erat quando hic adveni.
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-03 20:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 13:17 [gentoo-amd64] firefox 2 on amd64 Mark Haney
2007-01-03 13:20 ` Rob Lesslie
2007-01-03 13:35 ` Stefan Vunckx
2007-01-03 15:49 ` Mark Haney
2007-01-03 15:56 ` Rob Lesslie
2007-01-03 16:03 ` David Pyke
2007-01-03 16:08 ` Mark Haney
2007-01-03 16:14 ` Harry Holt
2007-01-03 18:52 ` [gentoo-amd64] X.Org troubles Andrei Korolyov
2007-01-03 18:58 ` David Pyke
2007-01-03 19:05 ` Andrei Korolyov
2007-01-03 19:05 ` Olivier Crete
2007-01-03 20:20 ` Richard Fish
2007-01-04 6:22 ` [gentoo-amd64] " Duncan
2007-01-04 8:47 ` Andrei Korolyov
2007-01-04 10:49 ` Duncan
2007-01-04 14:51 ` Ferris McCormick
2007-01-04 15:07 ` Markku Kaukinen
2007-01-04 15:22 ` Ferris McCormick
2007-01-04 15:33 ` Markku Kaukinen
2007-01-04 16:10 ` Ferris McCormick
2007-01-03 17:31 ` [gentoo-amd64] firefox 2 on amd64 Boyd Stephen Smith Jr.
2007-01-03 19:42 ` Daemon Xavier
2007-01-03 19:55 ` Boyd Stephen Smith Jr.
2007-01-03 22:34 ` Neil Bothwick
2007-02-26 13:50 ` Paul de Vrieze
2007-01-04 0:18 ` Joaquim Quinteiro Uchoa
2007-01-03 20:11 ` Mark Haney [this message]
2007-01-04 6:32 ` [gentoo-amd64] " Duncan
2007-01-04 13:35 ` Wil Reichert
2007-01-04 21:32 ` Duncan
2007-01-03 13:30 ` [gentoo-amd64] " Boyd Stephen Smith Jr.
2007-01-04 8:08 ` [gentoo-amd64] OT, Ciaran sig quote, reference? Was: " Duncan
2007-01-04 10:52 ` Bo Ørsted Andresen
2007-01-04 21:30 ` [gentoo-amd64] " Duncan
2007-01-05 14:59 ` Duncan
2007-01-06 0:30 ` [gentoo-amd64] " Regis Decamps
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=459C0E03.3080003@ercbroadband.org \
--to=mhaney@ercbroadband.org \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox