There are new version of mongodb is available. The release contains fixes for 40 issues: https://jira.mongodb.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+SERVER+AND+fixVersion+%3D+%222.2.1%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide Reproducible: Always
Hey Mike, it's in tree now :) *mongodb-2.2.1 (04 Nov 2012) *mongodb-2.2.0-r2 (04 Nov 2012) *mongodb-2.0.7-r2 (04 Nov 2012) *mongodb-2.0.7-r1 (04 Nov 2012) 04 Nov 2012; <alexys@gentoo.org> +files/mongodb-2.0-r1-boost-1.50.patch, -mongodb-2.0.7.ebuild, +mongodb-2.0.7-r1.ebuild, +mongodb-2.0.7-r2.ebuild, -mongodb-2.2.0.ebuild, +mongodb-2.2.0-r2.ebuild, +files/mongodb-2.2-r2-boost-1.50.patch, +mongodb-2.2.1.ebuild: Fix boost-1.50 build for 2.x series, fix #425190, use -r1 versions for older boost, use -r2 for >=1.50 boost. No longer depend on spidermonkey-1.7 for all the 2.x series wrt #390631. Note that v1.8.5 will be dropped later wrt #376983. Version bump fix #441586. Drop old stuff.
Could you clarify why boost-1.50 is mandatory for mongodb-2.2.1?
(In reply to comment #2) > Could you clarify why boost-1.50 is mandatory for mongodb-2.2.1? Because that's the way it's going for upstream as this patch was applied and is thus scheduled on the next releases. I agree that it's not really mendatory today, that's why I created -r1 and -r2 versions for 2.2 and 2.0.7 versions but I think users willing to have the most up to date release should prepare for boost-1.50 anyway + it's less a packaging nightmare to keep up to date with.
