Package Managers Compared: apt, dnf, pacman, zypper

2026-06-06 Reading time: About 12 min Difficulty: Intermediate

What is a package manager?

Conclusion: A package manager installs, updates, removes, and resolves dependencies for software. Distros name it differently — apt, dnf, pacman, zypper — but the job is the same.

On Linux you do not hunt down individual installers like on Windows. A package manager pulls the target package from a central repository and automatically resolves its dependencies (the other libraries it needs).

The goal of this guide is to put the four major package managers on one map. The command names differ, but the pattern of operations is shared: refresh the index, install, search, remove. Learn the pattern and you will not get lost on a distro you have never touched.

Why does each distribution differ?

Conclusion: The package format (.deb, .rpm, etc.) and the design philosophy that manages it differ by distro family. The major families are Debian, Red Hat, Arch, and SUSE.

Historically each distro evolved its own package management. As a result, the format and the tools split along family lines.

The "high-level tool" handles repository fetching and dependency resolution; the "low-level tool" unpacks and registers a single package file. You mostly touch the high-level side, but the relationship is covered below.

The apt map (Debian / Ubuntu family)

Conclusion: apt is the most widely used high-level tool. The basic pattern is sudo apt update to refresh the index, then sudo apt install <package>.

Used on Debian, Ubuntu, and their derivatives. apt is the interactive front end that unifies the older apt-get / apt-cache.

# Refresh the index (package list)
$ sudo apt update

# Upgrade all installed packages
$ sudo apt upgrade

# Install a package
$ sudo apt install nginx

# Remove (keep config files)
$ sudo apt remove nginx

# Remove including config files
$ sudo apt purge nginx

# Search / show info
$ apt search keyword
$ apt show nginx

The dnf map (Fedora / RHEL family)

Conclusion: dnf is the standard tool of the Red Hat family and the successor to yum. Unlike apt, it refreshes metadata automatically when you run a command.

Used on Fedora, RHEL 8+, Rocky Linux, and AlmaLinux. The yum command usually remains as an alias to dnf.

# Upgrade the whole system (metadata fetch is automatic)
$ sudo dnf upgrade

# Only check what can be updated
$ dnf check-update

# Install a package
$ sudo dnf install nginx

# Remove
$ sudo dnf remove nginx

# Search / show info
$ dnf search keyword
$ dnf info nginx

The pacman map (Arch family)

Conclusion: pacman is driven by short option letters. The building blocks are -S (sync = install), -R (remove), -Q (query), -y (refresh DB), and -u (upgrade).

Used on Arch Linux and Manjaro. Fastest once it clicks, but the symbolic options confuse newcomers at first.

# Sync the package DB and fully upgrade the system (most common)
$ sudo pacman -Syu

# Install a package
$ sudo pacman -S nginx

# Remove (also drop now-unneeded dependencies)
$ sudo pacman -Rs nginx

# Search (remote) / show info (remote)
$ pacman -Ss keyword
$ pacman -Si nginx

# List installed packages
$ pacman -Q

The zypper map (openSUSE family)

Conclusion: zypper is the standard tool of openSUSE / SLE. Its flow — refresh (update index), then install / update — is close to apt. Each subcommand has a short form.

Used on openSUSE Leap / Tumbleweed and SUSE Linux Enterprise. The format is .rpm, but the tool is a different lineage from dnf.

# Refresh the repository index
$ sudo zypper refresh

# Update installed packages
$ sudo zypper update

# Install a package (short form: in)
$ sudo zypper install nginx

# Remove (short form: rm)
$ sudo zypper remove nginx

# Search (short form: se) / show info
$ zypper search keyword
$ zypper info nginx

The four-command comparison table

Conclusion: Line the tools up by operation (update, install, remove, search) and you can work on any unknown distro just by reading the table. This is the map at the heart of this guide.

How do dpkg / rpm relate to all this?

Conclusion: dpkg / rpm are low-level tools that operate directly on a single package file. They do not resolve dependencies, so use a high-level tool (apt / dnf, etc.) when you want dependencies handled automatically.

Use a low-level tool when you want to install a downloaded .deb / .rpm directly.

# Install a .deb directly (does not resolve dependencies)
$ sudo dpkg -i package.deb

# Install a .rpm directly (does not resolve dependencies)
$ sudo rpm -i package.rpm

How do you choose and migrate?

Conclusion: You do not really "choose" — the distro decides for you. When migrating, translate commands via the table, and additionally watch out for partial upgrades on rolling distros (Arch / Tumbleweed).

The practical decision points:

• Server operations: Ubuntu (apt) and the RHEL family (dnf) dominate. If you write Dockerfiles, learn the install syntax for both.
• Desktop / cutting edge: Arch (pacman) or Fedora (dnf). Get used to the pacman -Syu discipline.
• Enterprise: the SUSE family (zypper). Mind the difference between zypper dup and update.
• When migrating: commands map 1:1 via the comparison table. The two things that trip people up are "is the index refresh automatic or manual" and "rolling or fixed release".