Opened 13 years ago
Closed 12 years ago
#31159 closed update (fixed)
mongodb: update to version 2
| Reported by: | drew@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | haspatch | Cc: | richard@…, tim.hawkins@… |
| Port: | mongodb |
Description
Please add support for MongoDB 2.0. Currently the latest supported version is 1.8.2
Attachments (2)
Change History (13)
comment:1 follow-up: 2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Milestone: | MacPorts 2.0.4 |
| Port: | mongodb added |
| Summary: | MongoDB 2.0 Addition → mongodb: update to version 2 |
| Type: | request → update |
| Version: | 2.0.3 |
comment:2 Changed 13 years ago by drew@…
Replying to ryandesign@…:
In r83628 I have updated mongodb to 1.8.3, the latest stable version.
Mongodb 2 is not released yet; the latest version available is 2.0.0-rc2, which is a release candidate, which means it is not a stable version yet. So it would not be appropriate to update the mongodb port to that version.
According to the preliminary mongodb 2 release notes, "Although the major version number has changed, MongoDB 2.0 is a standard, incremental production release and works as a drop-in replacement for MongoDB 1.8." So once mongodb 2 is released, we should be able to update the mongodb port to it and existing software should continue to work. It doesn't seem like we need to create a separate mongodb2 port.
If we wanted to offer users the chance to try out mongodb 2 before it's released, we could create a new mongodb-devel port for version 2.0.0-rc2. If version 2 final will be released soon, it may not be worth the effort.
MongoDB 2.0 was released today. http://blog.mongodb.org/post/10126837729/mongodb-2-0-released
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
It does not build. I have filed a bug report about that.
Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Attachment: | mongodb-2.0.0.diff added |
|---|
patch that does not work
comment:4 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
I've attached the patch I used to try to update the port.
comment:6 Changed 12 years ago by tim.hawkins@…
mongodb has 2.0 has been released for 4 weeks now, and is currently at 2.0.1. would it be possible to upgrade to this new version
comment:7 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
I would love to, but as I explained above, no, it is not possible, because of a bug in MongoDB.
It looks like the problem will be resolved in mongodb 2.0.2, so we can try to update when that's released. Or, if we can identify the diff that fixed the problem, we could try applying it to the 2.0.1 sources. Unfortunately the developers did not explain in the bug report how they fixed it.
comment:8 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | tim.hawkins@… added |
|---|
Tim, please see my remark in the ticket.
comment:9 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Correction: it looks like it's scheduled to be fixed in 2.0.2 but has not been fixed yet.
Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Attachment: | mongodb-2.0.1.diff added |
|---|
proposed patch
comment:10 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… removed |
|---|---|
| Keywords: | haspatch added |
| Owner: | changed from macports-tickets@… to ryandesign@… |
| Status: | new → assigned |
I've managed to build 2.0.1 with the attached patch. I want to test it a bit before committing it; feel free to try it if you're anxious to upgrade. I recommend you apply the update from #31797 first; I did.
comment:11 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
In r83628 I have updated mongodb to 1.8.3, the latest stable version.
Mongodb 2 is not released yet; the latest version available is 2.0.0-rc2, which is a release candidate, which means it is not a stable version yet. So it would not be appropriate to update the mongodb port to that version.
According to the preliminary mongodb 2 release notes, "Although the major version number has changed, MongoDB 2.0 is a standard, incremental production release and works as a drop-in replacement for MongoDB 1.8." So once mongodb 2 is released, we should be able to update the mongodb port to it and existing software should continue to work. It doesn't seem like we need to create a separate mongodb2 port.
If we wanted to offer users the chance to try out mongodb 2 before it's released, we could create a new mongodb-devel port for version 2.0.0-rc2. If version 2 final will be released soon, it may not be worth the effort.