Yum (software)

Yum (software)
Thomei08 · Public domain · source
Name	Yum
Developer	Red Hat, Fedora Project
Released	2003
Latest release	(varies by distribution)
Programming language	Python
Operating system	Linux
Genre	Package manager
License	GNU GPL

Yum (software) Yum is a package-management utility for RPM-based Linux distributions developed in the early 2000s to automate package installation, update, and dependency resolution. It integrates with RPM and repository metadata to provide transactional operations across packages for distributions maintained by organizations such as Red Hat, Fedora, CentOS, and SUSE. Yum has been influential in the evolution of package management alongside projects from Debian, Canonical, and Arch Linux communities.

Overview

Yum operates as a front end to RPM, coordinating package metadata, dependency resolution, and repository access used by distributions like Red Hat Enterprise Linux, Fedora Project, CentOS, Scientific Linux, and Mageia. It leverages Python libraries and RPM bindings to perform tasks comparable to tools from Debian Project, Canonical (company), and SUSE. System administrators from enterprises such as IBM, Oracle Corporation, Amazon (company), and Google encounter Yum workflows when provisioning virtual machines in environments managed by OpenStack Foundation, Kubernetes, and Docker, Inc..

History and Development

Yum originated as a community-driven project influenced by package management efforts at Red Hat and contributions from the Fedora Project engineering teams. Its timeline includes interactions with initiatives from CentOS Project, coordination with standards from the Open Source Initiative, and adoption patterns seen in deployments by NASA, Stanford University, and MIT. Major events affecting development included shifts in stewardship within organizations like Red Hat, Inc. and technical discussions involving collaborators from GNOME Foundation, X.Org Foundation, and Linux Foundation. Architectural decisions were informed by earlier package tools referenced in work coming out of Debian Project and experimental packaging used at University of California, Berkeley computing clusters.

Features and Architecture

Yum provides features for automated dependency resolution, transaction rollbacks, and repository metadata caching, implemented with Python modules analogous to libraries used in projects at Apache Software Foundation and Mozilla Foundation. Its architecture includes back ends that interact with RPM Package Manager internals, plugin mechanisms inspired by GNU Project philosophies, and configuration patterns consistent with practices at Red Hat and Fedora Project. Integration points exist for system management suites such as Ansible, Puppet, Chef (company), and SaltStack, enabling orchestration across infrastructures used by NASA, CERN, and European Commission research computing.

Usage and Commands

Administrators use Yum commands for installing, updating, removing, and querying packages with a CLI influenced by historical conventions from Red Hat tooling and command syntax familiar to users migrating from dpkg-based environments maintained by Debian Project. Typical commands invoked in shell environments on distributions maintained by CentOS Project or Fedora Project include package installation, group management, and repository operations integrated into automation workflows by teams at Netflix and Spotify. Logging and transaction output are often parsed by monitoring systems from Prometheus (software), Nagios, and Zabbix SIA deployments in enterprise contexts like Facebook and Twitter, Inc..

Repositories and Package Management

Yum relies on repository metadata standards compatible with mirrors hosted by communities and commercial entities such as CentOS Project, EPEL, Remi Collet, and vendor repositories provided by Red Hat. Repository management practices draw on mirror networks and content delivery strategies employed by organizations like Cloudflare, Akamai Technologies, and Fastly. Policies for package signing and distribution are coordinated with certificate authorities and security guidance from OpenPGP, FIPS, and compliance teams at institutions such as US Department of Defense and European Union Agency for Cybersecurity.

Comparison and Alternatives

Yum is often compared with alternative package managers including APT (software), DNF, Zypper, and Pacman (package manager), each associated with distinct distributions like Debian Project, Fedora Project, openSUSE, and Arch Linux. Decisions to choose Yum or successors involve considerations similar to migrations undertaken by corporations like Red Hat and IBM and cloud providers including Amazon Web Services and Microsoft Azure. Community-driven alternatives and forks have arisen in contexts associated with projects such as CentOS Stream, AlmaLinux, and Rocky Linux.

Security and Extensibility

Yum supports GPG signature verification and plugin extensibility that enables integration with security tooling from vendors like Red Hat, Tripwire, and McAfee. Its extensibility model allows third-party modules used by compliance teams at Deloitte, PwC, and KPMG to enforce policies, while vulnerability scanning integrations interface with services maintained by NIST, MITRE Corporation, and CVE Program. Plugin ecosystems mirror extensibility approaches seen in projects from the Apache Software Foundation and encourage contributions from individual developers affiliated with universities and companies such as Google and Microsoft.

Category:Package management software