public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox
Date: Sat, 04 Feb 2006 14:32:06 +0100	[thread overview]
Message-ID: <43E4ACD6.10203@planet.nl> (raw)
In-Reply-To: <200602040809.34067.ddjones@riddlemaster.org>

Daniel D Jones schreef:
> I'd like to run Firefox 1.5.  The latest stable build appears to be 
> 1.07.  I added ww-client/mozilla-firefox ~x86 to my package.keywords
>  file, which resulted in Deer Park being installed.  I don't want
> Deer Park, just the 1.5 release version.

The version labelled as Deer Park under Gentoo *is* the 1.5 release
version, to the best of my knowledge.

As I understand it, there is a licensing requirement from the Mozilla
group that specifies that compiled versions provided by anyone other
than Mozilla.org cannot use the 'official' branding. Therefore, the
release displays "Deer Park" but is otherwise identical (built from the
same source release tarball as the Mozilla.org compiled release, just
not built by Mozila.org, but by you or the Gentoo devs).

Apparently you can 'fix' this (if it must be fixed) by activating the
./configure switch --enable-official-branding. You can of course do this
by copying the current ebuild to your PORTDIR_OVERLAY, making the
adjustment, and compiling that instead, or by --as you said-- installing
or compiling the official Mozilla binary or source from the Mozilla.org
site.

Check the forums, I believe that that's where I discovered what
information I know about this issue.

> I've considered downloading the source and manually installing but 
> I'd prefer not to do something which may confuse portage at some 
> point.  Thanks for any suggestions.

That's what Portage overlay directories are for; to do something like
this without confusing Portage. Self-regulating, of course-- if the
issue is not important enough to the user to make it worth their while
to learn how to set up an overlay, and how to populate it with the
relevant ebuilds (especially if the relevant ebuild must be created from
scratch rather than just adjusted), then the issue is not necessarily
important enough to  warrant "solving", offering the user an opportunity
to re-evaluate the severity  of the issue. As with all things Gentoo,
it's your choice as to how you want to handle it.

Holly
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-02-04 13:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-04 13:09 [gentoo-user] Firefox Daniel D Jones
2006-02-04 13:26 ` Beau E. Cox
2006-02-04 14:09   ` Daniel D Jones
2006-02-04 16:37     ` Holly Bostick
2006-02-04 17:02       ` Daniel D Jones
2006-02-04 18:20         ` Chan Min Wai
2006-02-04 19:40           ` [gentoo-user] Firefox Simon Kellett
2006-02-05 17:21             ` Roy Wright
2006-02-04 19:01         ` [gentoo-user] Firefox Holly Bostick
2006-02-04 13:30 ` Andrew Gaydenko
2006-02-04 13:32 ` Holly Bostick [this message]
2006-02-04 13:36 ` Scott Stoddard
  -- strict thread matches above, loose matches on Subject: below --
2011-06-27 23:52 Daniel D Jones
2011-06-28  0:44 ` Albert Hopkins

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=43E4ACD6.10203@planet.nl \
    --to=motub@planet.nl \
    --cc=gentoo-user@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