Created attachment 164494 [details] databases/mongodb32 patch Based loosely on the MongoDB 2.6 port, this provides MongoDB 3.2 plus the now separate MongoDB tools. The tools have been rewritten in Go, and are provided separately to the core distribution. It is also worth noting that with 3.6, i386 is a deprecated architecture as per MongoDB release documents. Looking forward to your feedback.
Nice work Brendan! Can you include the addition of the two ports to the databases/Makefile please Thank yoU!
Attachment for the mongodb32-tools port is missing. Could you please send an attachment for the mongodb32-tools port? Thank you.
I'll take it. 1) As already noted, you forgot to attach a port for mongodb32-tools 2) Why separate port? Is 3.2 version incompatible with 2.6 currently in ports?
I think there is no real reason for this to be a separate port from version 2.6 currently in ports, because there is no feature regression with this version. But the tools (databases/mongodb32-tools) were part of the databases/mongodb port in the version 2.6 that is currently in the ports, so tools must be added to ports collection. btw. license is AGPL3, not dual any more because C++ driver is separated in version 3.2 (devel/mongo-cxx-driver port).
Okay, I am adding ale@ for feedback: what do you think if we update the existing mongodb port with the proposed version?
(In reply to Dmitry Sivachenko from comment #3) 1) Apologies, I have been busy with several other things and overlooked this until now. I will send updated patches tomorrow. 2) There were a few compatibility changes as of v3.0 <https://docs.mongodb.org/manual/release-notes/3.0-compatibility/> and v3.2 changes the default storage engine <https://docs.mongodb.org/manual/release-notes/3.2-compatibility> so I took the conservative option and offered it as a separate port, seeing as it also introduces the tools as a separate codebase now. I am happy to offer this as a patch to the current mongodb port plus a new port with the tools if that's considered a better option however.
(In reply to numisemis from comment #4) The information about the license is interesting, as their repositories still contain both licenses, and that's why I referred to both still. Happy to drop APACHE2 from the Makefile if this is considered appropriate.
Created attachment 165055 [details] mongodb32-tools shar Apologies about the delay, I had to fix some issues with the port that I had apparently overlooked before.
Thanks for the mongodb-tools port, let's wait for ale's decision if it is OK to update the existing port.
Alex, what is your opinion? Should we create separate mongodb32 port or it is OK for you to upgrade the existing mongodb port?
I use the existing Mongo port in production on FreeBSD, so I thought I'd offer my 2¢. My preference would be to retain Mongo 2.6 and update it to the latest 2.6.11 version so that those still using 2.6 in production can continue to do so. Mongo 3.20 is new and has had some issues; for example 3.21 has just been released to fix a serious issue with replica sets: https://jira.mongodb.org/browse/SERVER-21868 Has creating a mongo3 (rather than mongodb32) port been considered? Or would the plan be to create mongodb33 etc. as they're released? Thanks for all your work in bringing Mongo 3 to ports.
If it is just an error in existing 3.2 version, it should not stop us to update mongodb, because every version has some errors. According to numisemis@yahoo.com earlier in this thread, "there is no feature regression with this version". But I am personally fine with separate mongodb3 port if people consider this beneficial, but I will wait a bit more in hope to get ale@'s comments.
I'm currently using Mongo 2.x in production on FreeBSD and would personally prefer to see the 2.x series continue alongside the new 3.x branch (brilliant!). The typical approach (in my experience of FreeBSD) in such a situation would be for either a databases/mongodb3 to be created (whilst their new codebase settles) and for the 2.x to continue to be updated (I had been considering submitting a PR to bring it up to date) - or - for the current databases/mongodb port to become databases/mongodb2 and this new port to become databases/mongo.
A commit references this bug: Author: demon Date: Sat Jan 23 12:46:59 UTC 2016 New revision: 406969 URL: https://svnweb.freebsd.org/changeset/ports/406969 Log: Add a port for mongodb version 3.2. PR: 205510 Submitted by: Brendan Molloy <brendan+freebsd@bbqsrc.net> Maintainer of databases/mongodb port timeout (3 weeks) I bumped version to 3.2.1. mongodb32-tools port coming soon. Changes: head/databases/mongodb32/ head/databases/mongodb32/Makefile head/databases/mongodb32/distinfo head/databases/mongodb32/files/patch-SConstruct head/databases/mongodb32/files/patch-src_mongo_SConscript head/databases/mongodb32/files/patch-src_mongo_db_kill_current_op.cpp head/databases/mongodb32/files/patch-src_mongo_db_ops_modifier_push.cpp head/databases/mongodb32/files/patch-src_third_party_boost_libs_filesystem_v3_src_path.cpp head/databases/mongodb32/pkg-plist
A commit references this bug: Author: demon Date: Sat Jan 23 14:36:27 UTC 2016 New revision: 406994 URL: https://svnweb.freebsd.org/changeset/ports/406994 Log: New port: mongodb32-tools. Extra tools factored out from mongodb port in version 3. PR: 205510 Submitted by: Brendan Molloy <brendan+freebsd@bbqsrc.net> Changes: head/databases/Makefile head/databases/mongodb32-tools/ head/databases/mongodb32-tools/Makefile head/databases/mongodb32-tools/distinfo head/databases/mongodb32-tools/files/ head/databases/mongodb32-tools/files/patch-vendor_src_github.com_spacemonkeygo_openssl_build.go head/databases/mongodb32-tools/files/patch-vendor_src_github.com_spacemonkeygo_openssl_init__posix.go head/databases/mongodb32-tools/pkg-descr head/databases/mongodb32-tools/pkg-plist
New ports added, thanks!!