Raúl Porcel a écrit :
So, firefox-3, seamonkey-2, thunderbird-3 and other mozilla products will be using xulrunner-1.9, which is the codebase the mozilla products are based on. In fact, everytime you emerge any of those apps, you're compiling xulrunner, which takes 90% of the time to build. The good thing about those new versions, is that they'll be capable of using the xulrunner library installed of the system. So you only have to build xulrunner once, and you could build firefox-3, seamonkey-2, thunderbird-3 against it, and firefox-3 takes less than two minutes to build with shared xulrunner.
Brilliant! I thought they had dropped the idea of using xulrunner. Great to hear this!
Since firefox-3 seems usable now, i was thinking on adding it to the tree, however that'll need to add net-libs/xulrunner-1.9. Some apps use xulrunner at the moment[3], instead of building against firefox or thunderbird or seamonkey. Xulrunner is not mandatory to build firefox-3, in fact you can build firefox only with the current ebuilds in the overlay.
Do firefox and seamonkey still provide their own gtkmoz-embed? Are they still different (ie, almost the same, but not quite entirely 100% the same, although if you look at them they really look the same, but really they're not?)
My other question is this, can't we do a big community thing à la Bug Day where we make sure that all the apps that currently have firefox/seamonkey/xulrunner use flags all build against xulrunner 1.9 and drop all other keywords for the sake of simplicity?
Anyhow, I'd say mask ff3 and xulrunner 1.9. Better fix things for real instead of having our own hand-made workarounds.
Cheers, Rémi -- gentoo-dev@lists.gentoo.org mailing list
