| Yellowdog Updater, Modified | |
| YUM | |
| Developer: | Seth Vidal |
| Released: | [1] [2] |
| Programming Language: | Python[3] |
| Operating System: | Linux, AIX, IBM i, ArcaOS |
| Platform: | RPM |
| Genre: | Package management system |
| License: | GPLv2 |
The Yellowdog Updater Modified (YUM) is a free and open-source command-line package-management utility for computers running the Linux operating system using the RPM Package Manager.[4] Though YUM has a command-line interface, several other tools provide graphical user interfaces to YUM functionality.
YUM allows for automatic updates and package and dependency management on RPM-based distributions.[5] Like the Advanced Package Tool (APT) from Debian, YUM works with software repositories (collections of packages), which can be accessed locally[6] or over a network connection.
Under the hood, YUM depends on RPM, which is a packaging standard for digital distribution of software, which automatically uses hashes and digital signatures to verify the authorship and integrity of said software; unlike some app stores, which serve a similar function, neither YUM nor RPM provide built-in support for proprietary restrictions on copying of packages by end-users. YUM is implemented as libraries in the Python programming language, with a small set of programs that provide a command-line interface. GUI-based wrappers such as YUM Extender (yumex) also exist, and has been adopted for Fedora Linux until version 22.[7]
A rewrite of YUM named DNF replaced YUM as the default package manager in Fedora 22 (in 2015). This was required due to Fedora's transition from Python 2 to Python 3, which isn't supported by YUM.[8] DNF also improves on YUM in several ways - improved performance, better resolution of dependency conflicts, and easier integration with other software applications.[9] From RHEL 8, yum is an alias for DNF.[10]
The original package manager, Yellowdog UPdater (YUP) was developed in 1999-2001 by Dan Burcaw, Bryan Stillwell, Stephen Edie, and Troy Bengegerdes at Terra Soft Solutions (under the leadership of then CEO Goutham Krishna) as a back-end engine for a graphical installer of Yellow Dog Linux.
As a full rewrite of YUP, YUM evolved primarily to update and manage Red Hat Linux systems used at the Duke University Department of Physics by Seth Vidal and Michael Stenner. Vidal continued to contribute to YUM until his death in a Durham, North Carolina bicycle accident on 8 July 2013.[11] [12] [13]
In 2003 Robert G. Brown at Duke published documentation for YUM.[14] Subsequent adopters included[14] Fedora, Rocky Linux, AlmaLinux, CentOS, and many other RPM-based Linux distributions, including Yellow Dog Linux itself, where YUM replaced the original YUP utility — last updated on SourceForge in 2001.[15] By 2005, it was estimated to be in use on over half of the Linux market, and by 2007 YUM was considered the "tool of choice" for RPM-based Linux distributions.[16]
YUM aimed to address both the perceived deficiencies in the old APT-RPM,[17] and restrictions of the Red Hat up2date package management tool. YUM superseded up2date in Red Hat Enterprise Linux 5 and later.[18] Some authors refer to YUM as the Yellowdog Update Manager, or suggest that "Your Update Manager" would be more appropriate.[19] [20] A basic knowledge of YUM is often included as a requirement for Linux system-administrator certification. The GNU General Public License of YUM allows the free and open-source software to be freely distributed and modified without any royalty, if other terms of the license are honored.
While yum was originally created for Linux, it has been ported to a number of other operating systems including AIX,[21] IBM i,[22] and ArcaOS.[23]
YUM can perform operations such as:
The 2.x versions of YUM feature an additional interface for programming extensions in Python that allows the behavior of YUM to be altered. Certain plug-ins are installed by default.[25] A commonly installed[26] package yum-utils, contains commands which use the YUM API, and many plugins.
Graphical user interfaces, known as "front-ends", allow easier use of YUM. PackageKit and Yum Extender (yumex) are two examples.[27] Yum Extender was deprecated for a while when Fedora migrated to DNF,[28] but it was rewritten in Python 3 and Gtk 3 and has been in progress for development. This brand-new Yum Extender is available for Fedora 34 or newer.
Information about packages (as opposed to the packages themselves) is known as metadata. These metadata are combined with information in each package to determine (and resolve, if possible) dependencies among the packages. The hope is to avoid a situation known as dependency hell. A separate tool, createrepo, sets up YUM software repositories, generating the necessary metadata in a standard XML format (and the SQLite metadata if given the -d option).[29] The mrepo tool (formerly known as Yam) can help in the creation and maintenance of repositories.[30]
YUM's XML repository, built with input from many other developers, quickly became the standard for RPM-based repositories.[31] Besides the distributions that use YUM directly, SUSE Linux 10.1[32] added support for YUM repositories in YaST, and the Open Build Service repositories use the YUM XML repository format metadata.
YUM automatically synchronizes the remote meta data to the local client, with other tools opting to synchronize only when requested by the user. Having automatic synchronization means that YUM cannot fail due to the user failing to run a command at the correct interval.[33] [34]