This is two changes for every package and sub-package of both community and enterprise: 1) Add the equivalent old package name to each package's Provides field 2) Add the equivalent old package name to each apckage's Conflicts field. Tested scenarios that should work: * Upgrading from 2.4.10 (Vs. uninstalling then installing) * Installing sub-packages with new name * Installing sub-packages with old name * Installing metapackage with new name * Installing metapackage with old name * Installing old versions of packages using new --exclude mongodb-org,mongodb-org-server syntax * Installing third party package that depends on old package name (new packages were automatically installed) (cherry picked from commit 5337c7e)
This change makes packaging text more consistent between rpms and debs, as well as bringing the text up to date with more recent verbiage.
The "Release" rpm field has previous been 'mongodb_1' in all RPM's but to support separate RHEL/CentOS 5.7+ and 6.2+ rpms, the release will now be '1.el5' and '1.el6'.
These are all based on equivalent "-unstable" files that have been used for 2.5 packages. The only differences are removing "-unstable" from package, directory, and file names, and replacing normal packages in conflicts with unstable packages.
…ongodb-org-unstable conflicts lists
This is one of two commits to clean up package dependencies. The next will be for Debian packages.
This sets resource limits across all Linux packages to match our recommended settings - http://docs.mongodb.org/manual/reference/ulimit/#recommended-settings
…r, mongodb-dev, and mongodb-clients Signed-off-by: Ernie Hershey <firstname.lastname@example.org>
This includes splitting rpm and .deb packages into sub-packages and externalizing the spec and control files to be maintained as static files.
Removed unneccessary whitespace so mongod.conf that ships in the RPM is consistent. Signed-off-by: Matt Kangas <email@example.com>