As spidermonkey in the portage tree is not going to be slotted, and both stable and ~arch versions are >=1.8.2 and not compatible with mongodb, please convert the build system of mongodb to use the embedded third_party/js-1.7 instead. If I have time i'll work on this, but since I know very little about scons it may take a while for me to create a working patch.
erm, my first thought is why would I do that exactly, it's not a good practice at all and we should avoid this by all means. I guess this question applies to you other bugs aswell related to mongodb : is your plan to remove totally spidermonkey-1.7 from tree ? If I were to spend some time on this matter, I would rather spend it trying to make mongodb work with spidermonkey-1.8 series.
Whether it stays in the tree or not, current stable is spidermonkey-1.8.2.15 and current ~arch is soon going to be spidermonkey-1.8.5-r1 .. there are a number of other packages in the tree that will depend on the newer spidermonkeys (i'm trying to upconvert everything to 1.8.5), and so forcing the downgrade will keep a lot of other packages from working on a user's system. I don't know if this matters or not, given the target use for mongodb (most other packages using spidermonkey-1.8.5 are desktop-related instead of server-related); but in terms of system-wide consistency it would be better to depend on either latest {stable,~arch} or use the embedded copy (which iirc is the only one officially supported by mongodb upstream)
(In reply to comment #2) > I don't know if this matters or not, given the target use for mongodb (most > other packages using spidermonkey-1.8.5 are desktop-related instead of > server-related); but in terms of system-wide consistency it would be better to > depend on either latest {stable,~arch} or use the embedded copy (which iirc is > the only one officially supported by mongodb upstream) This is indeed a quite specific server-minded application and as much as I'd love it to be system-wide consistent, my main focus is to have it clean and working on Gentoo for production servers. I've already discussed and motivated this matter with upstream so I'm just gonna link you to it [1]. To answer fully your question, upstream confirmed to me that they did NOT modify the shipped third_party/js-1.7, so our current mongodb-2.0.2_rc0 dependency is in line with the the officially supported version of spidermonkey. [1] http://groups.google.com/group/mongodb-dev/browse_thread/thread/38e8c30606a300c3
I agree with Ultrabug here. The only "benefit" I can see is dropping an older version of spidermonkey from our tree, which is negligible in my opinion. I'm going to close this as WONTFIX if you guys don't have any other remarks.
