RPMs

RPMs refer to packages used by the RPM Package Manager, a widely adopted packaging system for Red Hat–based Linux distributions. An RPM (Red Hat Package Manager) file has a .rpm extension and contains compiled software, along with metadata such as name, version, release, architecture, dependencies, and scripts to run before or after installation. RPMs can be signed to verify authenticity and integrity.

The RPM Package Manager is both a package format and a toolchain for managing those packages. It maintains a database of installed packages and provides capabilities to install, upgrade, verify, query, and remove software. Typical binary RPMs are complemented by source RPMs (.src.rpm) that include the original source code and build instructions. The system uses metadata to express dependencies, which front-end package managers resolve by fetching required packages from repositories.

Usage commonly occurs through high-level front-ends such as DNF or YUM on Red Hat-based systems, which automate dependency resolution and repository handling. The lower-level rpm command offers direct actions: rpm -i installs, rpm -U upgrades, rpm -e erases, rpm -q queries, rpm -V verifies, and rpm -l or -p lists or inspects packages. RPMs can also be installed from local files or repositories, and they can be verified for integrity and authenticity via digital signatures.

Distribution scope includes Fedora, Red Hat Enterprise Linux, CentOS, and other RPM-based systems, as well as openSUSE, which uses RPM alongside its own tooling. The RPM ecosystem supports both binary packages for end users and source packages for building software from source.