When comparing Conda vs RPM (RPM Package Manager), the Slant community recommends RPM (RPM Package Manager) for most people. In the question“What are the best Linux package managers?” RPM (RPM Package Manager) is ranked 5th while Conda is ranked 16th. The most important reason people chose RPM (RPM Package Manager) is:
This makes maintenance and support easy.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Binary installs
They are fast and reliable as they do not need to compile before installation.
Pro Allows for multiple environments
It is great for developers since you can easily switch between complete environments with different versions of packages, for testing and development.
Pro Open source
Conda is open source and on Github, so if you see something wrong you can fix it and submit a patch.
Pro Easy to create packages on non-rpm based distros
This makes maintenance and support easy.
Pro Follows the UNIX philosophy
It only does one thing and that well.
Pro Part of LSB
It is part of the Linux standard base.
Pro Very easy to create packages
It is very easy to create packages for it, you just need a small spec file.
Pro Standard archives
RPM packages are simple cpio archives that have additional compression support.
Pro Much more advanced than apt
Cons
Con Doesn't have everything
Conda is relatively new and has a smaller user-base, so the set of packages available is limited.
Con No way to resume downloads
Any download that is canceled or interrupted will have to be started over from the beginning as there is no built in solution for resuming downloads.
Con Installs huge collection of default unneeded libraries
Con No interaction
RPM does not support user interaction upon install.
Con Many forks
Currently there exist rpmv4, rpmv5 and distribution specific forks like Mandrake's urpm.
Con Plenty of different frontends
Almost any rpm distro has its own frontend for rpm there is zypper, yum, apt-rpm, dnf, poldek and many more.