For more evidence how this affects us see the "libmozjs-dev conflicts with firefox on Ubuntu" from today. Cheers Jan -- On 19 Nov 2009, at 18:35, Mikeal Rogers wrote: > The issue seems to be that some stuff was broken in Spidermonkey that didn't > effect Firefox or Thunderbird and the fixes for that stuff is still being > back ported. > > http://code.google.com/p/js18/wiki/BugzillaStatus > > -Mikeal > > On Thu, Nov 19, 2009 at 6:08 AM, Jan Lehnardt wrote: > >> >> On 19 Nov 2009, at 13:52, Dirkjan Ochtman wrote: >> >>> On Thu, Nov 19, 2009 at 13:47, Paul Davis >> wrote: >>>> I think this is the bug we want: >>>> https://bugzilla.mozilla.org/show_bug.cgi?id=479473 which was last >>>> updated in May. >>>> >>>> Most people are already on 1.8.1 libraries because packagers appear to >>>> have started pulling it from projects like XUL runner instead of >>>> building in isolation. >>> >>> I'm CC'ed on that one as well, but I think the consensus in #jsapi was >>> that they would release something called 1.8.0. The topic of releases >>> of SpiderMonkey is apparently not very popular with some of the crowd >>> there, though. >> >> Thanks for opening this thread Mikeal. I'd like to specifically call out >> the >> lack of releases or a clear release procedure or strategy to be a large >> problem for any dependent projects. >> >> On the latest Ubuntu this leads to situations where the built-in CouchDB >> is linked against libmoz.js from xulrunner. If you want to build a custom >> CouchDB, you need to specify the obscure and nonstandard xulrunner >> lib directory to build. But there is no obvious way to know, so people >> install libmozjs manually which conflicts with xulrunner, they don't know >> what xulrunner is and deinstall and all dependent packages which includes >> Firefox. >> >> This is a little bit unfortunate and I hope we can look forward to more >> predictable releases. >> >> Cheers >> Jan >> -- >> >>