From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Trouble decrypting message from firefox ebuild
Date: Sun, 18 Jan 2009 23:39:32 -0600 [thread overview]
Message-ID: <20090118233932.612b8c30@prezmyra.remarqs.net> (raw)
In-Reply-To: gl0vo0$mpe$3@ger.gmane.org
In <gl0vo0$mpe$3@ger.gmane.org>,
Grant Edwards <grante@visi.com> wrote:
> On 2009-01-18, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> But, I stand by my assertion that give just the message very many
> people are going to figure out that it means you need to replace the
> "firefox" use flag with the "xulrunner" use flag so that apps will
> build against firefox-3 instead of trying to build against firefox-2.
They won't build against Fx 3, they'll build against either Fx 2 or
xulrunner 1.8.1.x. Once you have Fx 3, you can't have Fx 2, but you
can still have the older xulrunner, since xulrunner is slotted.
> > Briefly:
> >
> > The gecko rendering engine was always part of firefox through
> > versions 1 and 2. This is plain silly as such a thing should
> > really be an independent block of code that stands alone and
> > everything else can use without requiring that all of firefox
> > be present.
> >
> > This has now been fixed, the engine is now in a package called
> > xulrunner which firefox builds against. Other apps also need
> > xulrunner, but if you keep "USE=firefox" intact those apps
> > will pull in all of firefox-2 just to get gecko. If you have
> > firefox-3 installed, you have an instant blocker. With
> > "USE=xulrunner" they will build against xulrunner and firefox
> > can be whatever you feel like installing.
>
> Now I'm confused. I thought xulrunner was the user-interface
> engine rather than the rendering engine.
xulrunner provides both gecko and the ABIs needed for using a UI made
of XUL.
--
»Q«
Kleeneness is next to Gödelness.
next prev parent reply other threads:[~2009-01-19 6:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 16:02 [gentoo-user] Trouble decrypting message from firefox ebuild Grant Edwards
2009-01-18 16:22 ` Alan McKinnon
2009-01-18 16:44 ` [gentoo-user] " Grant Edwards
2009-01-18 17:49 ` Alan McKinnon
2009-01-18 18:10 ` [OT] Re: [gentoo-user] " Willie Wong
2009-01-18 20:52 ` Alan McKinnon
2009-01-19 1:41 ` Dale
2009-01-19 4:41 ` [gentoo-user] Re: [OT] " Grant Edwards
2009-01-19 4:32 ` [gentoo-user] " Grant Edwards
2009-01-19 4:39 ` Dale
2009-01-19 5:39 ` »Q« [this message]
2009-01-19 7:19 ` Alan McKinnon
2009-01-19 16:17 ` Paul Hartman
2009-01-19 16:59 ` Grant Edwards
2009-01-19 17:30 ` Alan McKinnon
2009-01-19 17:39 ` Stroller
2009-01-19 18:15 ` Allan Gottlieb
2009-01-19 20:36 ` Grant Edwards
2009-01-20 12:10 ` Stroller
2009-01-20 17:08 ` Paul Hartman
2009-01-20 17:41 ` Grant Edwards
2009-01-18 17:03 ` Grant Edwards
2009-01-18 17:45 ` Mike Kazantsev
2009-01-19 1:43 ` Dale
2009-01-19 4:24 ` Grant Edwards
2009-01-19 4:34 ` Dale
2009-01-19 4:23 ` Grant Edwards
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=20090118233932.612b8c30@prezmyra.remarqs.net \
--to=boxcars@gmx.net \
--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