Currently the latest spidermonkey available in portage is 24.2.0, which was released in 2013. At https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Releases the current release is 45. What I'm looking for is a command-line javascript interpreter that supports the latest language features. SpiderMonkey 24 doesn't support, for example, the "rest operator" in destructuring.
Sure I can bump this. I haven't attempted to use the js shell in a very long time but I assume latest releases of seamonkey still include it.
GNOME will need spidermonkey 38 for being able to package GNOME-3.23.90. I am not sure if it will upgrade to 45 before final release or not, pretty sure it won't (.90 is already a beta). 38 seems to be considered a ESR, not sure about 45. But having both :38 and :45 slots would be nice for future readiness for us as well, but we'll definitely need :38. We require spidermonkey be compiled with --with-intl-api, but looks like this is just a spidermonkey[icu] dep then. Additionally we need a matching --enable/disable-cpp-rtti, as defined in mozjs build/autoconf/compiler-opts.m4, but if that isn't changed or USE flagged, we should be fine.
Spidermonkey is only released out of the mozilla ESRs. 38 was one version, 45 another, but in a few weeks both will be effectively obsolete upstream due to 52 coming out. Well, except that there still hasn't been any *official* release since 24.x (even 38 is jsut a release candidate). I'll package 38 right away, it's readly to go now except that there are two tests that are failing due to some missing dependencies from the rest of the firefox codebase. Once I have that sorted I'll commit it.
Anything left to do here?
(In reply to Mart Raudsepp from comment #4) > Anything left to do here? Well it's in place and relatively bug-free at this point, so I guess not. Let's close this one and any issues coming from it not being suitable for gnome's needs can be filed under new bugs.
