[DOCS-1240] Update package installation docs for version pinning in 2.4 Created: 15/Mar/13 Updated: 19/Mar/13 Due: 19/Mar/13 Resolved: 19/Mar/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ernie Hershey | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 48 weeks, 1 day ago |
| Description |
|
After talking to dan@10gen.com and samk, we should document how installation of different versions of packages will work once 2.4 is out. For example on these pages there are new mechanisms for specifying old versions: Using package names with versions in them will be deprecated but will still work: Debian/Ubuntu: We won't generate any packages named mongo22-*. Versions 2.2.x and 2.4.x (and future stable releases) will be available with these packages: RedHat/CentOS/Fedora: Debian/Ubuntu: Under the "Installing MongoDB" section there are two new relevant commands: 1) Installing a specific version: 2) Pinning to a specific version: I hope this is clear enough. I can help organize better or add more detail or make the actual changes. |
| Comments |
| Comment by auto [ 19/Mar/13 ] |
|
Author: {u'date': u'2013-03-18T21:58:23Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 19/Mar/13 ] |
|
Author: {u'date': u'2013-03-18T21:58:23Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |