FYI this will be finally slotted. Turns out it couldn't be slotted
because a patch we used that simulated xulrunner-1.8 pkgconfig files.
But since 99% of the stuff that depends on xulrunner-1.8 won't work with
xulrunner-1.9, those packages should be fixed by upstream, and they
should look for
Raúl Porcel wrote:
Xulrunner-1.9 is a big change, and the apps using it won't work until
they are fixed. So this needs to be decided, i've been working on
slotting xulrunner, and i'm ready to put it in the tree. However i'd
like to see what developers(since they will be the ones who will have
Okay, so here's the thing: Firefox 3 will be released probably some time
during this year, as you probably know, they released a few days ago
beta4 and beta5 will be out probably at the start of the next month or
so. I started doing ebuilds for net-libs/xulrunner-1.9 and
Hi,
Since the pkgconfig files for xulrunner-1.9 are renamed to avoid
collisions with current xulrunner-1.8.
In general I dont think that is a good idea to do that as you said
we'll have to patch all the rev deps of xulrunner. More importantly
we'll have to carry on those patches forever
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.
On 17:12 Sat 15 Mar , Raúl Porcel wrote:
That's what i would like to hear opinions about. Should we slot it, or
should we not slot it and wait until all the apps are fixed?
Favoring upstream's approach seems to better fit the Gentoo way. If
upstream doesn't intend it to be slotted,
