Details
-
Task
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
None
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:
http://docs.mongodb.org/manual/tutorial/install-mongodb-on-red-hat-centos-or-fedora-linux/
http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/
http://docs.mongodb.org/manual/tutorial/install-mongodb-on-debian/
Using package names with versions in them will be deprecated but will still work:
RedHat/CentOS/Fedora:
mongo18-10gen
mongo18-10gen-server
mongo20-10gen
mongo20-10gen-server
Debian/Ubuntu:
mongodb18-10gen
mongodb20-10gen
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:
mongo-10gen
mongo-10gen-server
Debian/Ubuntu:
mongodb-10gen
Under the "Installing MongoDB" section there are two new relevant commands:
1) Installing a specific version:
RedHat/CentOS/Fedora:
yum install mongo-10gen-server-2.2.3
Debian/Ubuntu:
apt-get install mongodb-10gen=2.2.3
2) Pinning to a specific version:
RedHat/CentOS/Fedora:
add "exclude=mongo-10gen,mongo-10gen-server" to /etc/yum.conf, or install the yum "versionlock" plugin and run "sudo yum versionlock mongo-10gen mongo-10gen-server"
Debian/Ubuntu:
echo mongodb-10gen hold | dpkg --set-selections
I hope this is clear enough. I can help organize better or add more detail or make the actual changes.