Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Portage vs RPM (RPM Package Manager), the Slant community recommends Portage for most people. In the question“What are the best Linux package managers?” Portage is ranked 2nd while RPM (RPM Package Manager) is ranked 5th. The most important reason people chose Portage is:
WIth portage you can decide and customize which dependencies to install through some thing called USE flags. These are keywords that when defined, will tell Portage that you want support for the chosen keyword.
Question Ranking
Pros
Pro Decide which dependencies to install
WIth portage you can decide and customize which dependencies to install through some thing called USE flags. These are keywords that when defined, will tell Portage that you want support for the chosen keyword.
Pro Sandboxes build process
Portage uses a sandbox as a safety measure during build processes. This is done to ensure that no packages accidentally write outside a 'safe' location.
Pro Can install multiple versions of the same package simultaneously
Slotting is a feature which allows users to install multiple versions of a software simultaneously. This is especially useful for libraries which have changed interfaces between versions.
Pro Allows both binary and source installation
With portage you can either compile packages from source or you can download and install their binary versions.
Pro Implements a standard with alternate implementations
If you need faster resolution, you can run pkgcore for search and portage for installing, and they work well together.
Pro Simple overlay management
Adding supplemental repositories, aka overlays, is easy with eselect-repository or layman.
Pro Respects customized config files
By default, portage doesn't delete or move any customized config files, thus enabling competent users to modify any config file however they want.
Pro You can view a list of programs that can be installed
With portage you can view a list of all the programs that you can install by going to /usr/portage and running ls.
Pro Full control over installed packages
You can fully control all packages if you use it properly.
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 High memory usage
Usually takes between 400-800MB of RSS (no problem to get over 1GB), so it's nothing for an old hardware.
Con Building from source take a lot of processing time
Most of Portage's pros are related to its "porting" process, building packages from source. This is very resource-intensive, with the few biggest packages sometimes taking even multiple hours to update or install.
Con Very slow
Dependency resolution is very slow and single-threaded, so usually you will see one of your cores running like crazy for over a minute.
Con Feature creep
It is very complicated and offers plenty of options.
Con You can not create packages under a non-portage distribution
Makes maintaining software for gentoo based systems a burden.
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.
