-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 2.5.3
-
Component/s: Packaging
-
Environment:Debian, Ubuntu, RHEL, CentOS
-
DevProd Build
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
As long as we have packages in our repo with "10gen" in the name, they're going to be confusing. We should figure out how to deprecate them.
For example, in Ubuntu:
ubuntu@ip-10-238-189-24:~$ sudo apt-cache search mongodb- libmongodb-perl - Mongo Driver for Perl mongodb-clients - object/document-oriented database (client apps) mongodb-dev - object/document-oriented database (development) mongodb-server - object/document-oriented database (server package) mongodb-10gen - An object/document-oriented database mongodb-10gen-unstable - An object/document-oriented database mongodb-10gen-unstable-mongos - An object/document-oriented database mongodb-10gen-unstable-server - An object/document-oriented database mongodb-10gen-unstable-shell - An object/document-oriented database mongodb-10gen-unstable-tools - An object/document-oriented database mongodb-org-unstable - An object/document-oriented database mongodb-org-unstable-mongos - An object/document-oriented database mongodb-org-unstable-server - An object/document-oriented database mongodb-org-unstable-shell - An object/document-oriented database mongodb-org-unstable-tools - An object/document-oriented database ubuntu@ip-10-238-189-24:~$
(The summaries listed are old, pre-SERVER-10920)
(unstable packages will go away pending SERVER-10874)
Maybe we should update the summaries to include "official" for mongodb-org* packages and "deprecated" or "legacy" for mongodb-10gen* packages.