1 |
In <gl0vo0$mpe$3@×××××××××.org>, |
2 |
Grant Edwards <grante@××××.com> wrote: |
3 |
|
4 |
> On 2009-01-18, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
5 |
|
6 |
> But, I stand by my assertion that give just the message very many |
7 |
> people are going to figure out that it means you need to replace the |
8 |
> "firefox" use flag with the "xulrunner" use flag so that apps will |
9 |
> build against firefox-3 instead of trying to build against firefox-2. |
10 |
|
11 |
They won't build against Fx 3, they'll build against either Fx 2 or |
12 |
xulrunner 1.8.1.x. Once you have Fx 3, you can't have Fx 2, but you |
13 |
can still have the older xulrunner, since xulrunner is slotted. |
14 |
|
15 |
> > Briefly: |
16 |
> > |
17 |
> > The gecko rendering engine was always part of firefox through |
18 |
> > versions 1 and 2. This is plain silly as such a thing should |
19 |
> > really be an independent block of code that stands alone and |
20 |
> > everything else can use without requiring that all of firefox |
21 |
> > be present. |
22 |
> > |
23 |
> > This has now been fixed, the engine is now in a package called |
24 |
> > xulrunner which firefox builds against. Other apps also need |
25 |
> > xulrunner, but if you keep "USE=firefox" intact those apps |
26 |
> > will pull in all of firefox-2 just to get gecko. If you have |
27 |
> > firefox-3 installed, you have an instant blocker. With |
28 |
> > "USE=xulrunner" they will build against xulrunner and firefox |
29 |
> > can be whatever you feel like installing. |
30 |
> |
31 |
> Now I'm confused. I thought xulrunner was the user-interface |
32 |
> engine rather than the rendering engine. |
33 |
|
34 |
xulrunner provides both gecko and the ABIs needed for using a UI made |
35 |
of XUL. |
36 |
|
37 |
-- |
38 |
»Q« |
39 |
Kleeneness is next to Gödelness. |