1 |
Okay, so here's the thing: Firefox 3 will be released probably some time |
2 |
during this year, as you probably know, they released a few days ago |
3 |
beta4 and beta5 will be out probably at the start of the next month or |
4 |
so. I started doing ebuilds for net-libs/xulrunner-1.9 and |
5 |
www-client/mozilla-firefox-3.0 in the mozilla overlay [1] since november |
6 |
2007, mainly thanks to Gergan Penkov's patches on his overlay, info |
7 |
available on the forums [2], which i've been adjusting them to do static |
8 |
releases and not livecvs ebuilds like he does. |
9 |
|
10 |
So, firefox-3, seamonkey-2, thunderbird-3 and other mozilla products |
11 |
will be using xulrunner-1.9, which is the codebase the mozilla products |
12 |
are based on. In fact, everytime you emerge any of those apps, you're |
13 |
compiling xulrunner, which takes 90% of the time to build. The good |
14 |
thing about those new versions, is that they'll be capable of using the |
15 |
xulrunner library installed of the system. So you only have to build |
16 |
xulrunner once, and you could build firefox-3, seamonkey-2, |
17 |
thunderbird-3 against it, and firefox-3 takes less than two minutes to |
18 |
build with shared xulrunner. |
19 |
|
20 |
Since firefox-3 seems usable now, i was thinking on adding it to the |
21 |
tree, however that'll need to add net-libs/xulrunner-1.9. Some apps use |
22 |
xulrunner at the moment[3], instead of building against firefox or |
23 |
thunderbird or seamonkey. Xulrunner is not mandatory to build firefox-3, |
24 |
in fact you can build firefox only with the current ebuilds in the overlay. |
25 |
|
26 |
Xulrunner-1.9 is a big change, and the apps using it won't work until |
27 |
they are fixed. So this needs to be decided, i've been working on |
28 |
slotting xulrunner, and i'm ready to put it in the tree. However i'd |
29 |
like to see what developers(since they will be the ones who will have to |
30 |
deal with this) and users prefer. Even if an app is compatible with |
31 |
xulrunner-1.9, it will have to be patched if we slot xulrunner. Since |
32 |
the pkgconfig files for xulrunner-1.9 are renamed to avoid collisions |
33 |
with current xulrunner-1.8. |
34 |
The other approach would be not slotting it, p.mask xulrunner-1.9 and |
35 |
wait until all the packages work against it and then unmask. |
36 |
That's what i would like to hear opinions about. Should we slot it, or |
37 |
should we not slot it and wait until all the apps are fixed? |
38 |
|
39 |
Obviously, not slotting it will require to wait until upstream or a |
40 |
developer patches the app to work with xulrunner-1.9. |
41 |
|
42 |
---------------------- |
43 |
|
44 |
On the other hand, you won't be able to use firefox-3, seamonkey-2, |
45 |
thunderbird-3 to build an app against, since what the apps needs is |
46 |
xulrunner, not firefox or seamonkey. |
47 |
So whatever is decided, please start fixing your ebuilds that use |
48 |
firefox, xulrunner, seamonkey or thunderbird, to stick the DEPEND to |
49 |
<www-client/mozilla-firefox-3,<www-client/seamonkey-2,<net-libs/xulrunner-1.9, |
50 |
<mail-client/mozilla-thunderbird-3 ASAP. |
51 |
|
52 |
Thanks |
53 |
|
54 |
[1] http://overlays.gentoo.org/proj/mozilla |
55 |
[2] http://forums.gentoo.org/viewtopic-t-556225.html |
56 |
[3] http://tinderbox.dev.gentoo.org/misc/rindex/net-libs/xulrunner |
57 |
-- |
58 |
gentoo-dev@l.g.o mailing list |