| YUM | |
|---|---|
 | |
 YUM running an update onFedora 16 | |
| Developer | Seth Vidal |
| Initial release | June 2002; 23 years ago (2002-06)[1][2] |
| Stable release | 3.4.3 / 28 June 2011; 14 years ago (28 June 2011) |
| Repository | |
| Written in | Python[3] |
| Operating system | Linux,AIX,IBM i,ArcaOS |
| Platform | RPM |
| Type | Package management system |
| License | GPLv2 |
| Website | yum |
TheYellowdog Updater Modified (YUM) is afree and open-sourcecommand-linepackage-management utility for computers running theLinuxoperating system using theRPM Package Manager.[4] Though YUM has a command-line interface, several other tools providegraphical user interfaces to YUM functionality.
YUM allows for automatic updates and package and dependency management on RPM-based distributions.[5] Like theAdvanced Package Tool (APT) fromDebian, YUM works withsoftware repositories (collections of packages), which can be accessed locally[6] or over a network connection.
Under the hood, YUM depends onRPM, which is a packaging standard fordigital distribution of software, which automatically useshashes anddigital signatures to verify the authorship and integrity of said software; unlike someapp stores, which serve a similar function, neither YUM nor RPM provide built-in support forproprietary restrictions on copying of packages by end-users. YUM is implemented as libraries in thePython programming language, with a small set of programs that provide acommand-line interface.[7] GUI-based wrappers such as YUM Extender (yumex) also exist,[8] and has been adopted for Fedora Linux until version 22.[9]
A rewrite of YUM namedDNF replaced YUM as the default package manager inFedora 22[9] (in 2015). This was required due to Fedora's transition from Python 2 to Python 3, which is not supported by YUM.[10] DNF also improves on YUM in several ways - improved performance, better resolution of dependency conflicts, and easier integration with other software applications.[11] FromRHEL 8, yum is an alias forDNF.[12]
The original package manager, Yellowdog UPdater (YUP) was developed in 1999-2001 by Dan Burcaw, Bryan Stillwell, Stephen Edie, and Troy Bengegerdes atTerra Soft Solutions (under the leadership of then CEOKai Staats) as a back-end engine for a graphical installer ofYellow Dog Linux.[4]
As a full rewrite of YUP, YUM evolved primarily to update and manageRed Hat Linux systems used at theDuke University Department of Physics by Seth Vidal and Michael Stenner. Vidal continued to contribute to YUM until his death in aDurham, North Carolina bicycle accident on 8 July 2013.[13][14][15]
In 2003Robert G. Brown at Duke published documentation for YUM.[7] Subsequent adopters included[7]Fedora,Rocky Linux,AlmaLinux,CentOS, and many other RPM-basedLinux distributions, includingYellow Dog Linux itself, where YUM replaced the original YUP utility — last updated onSourceForge in 2001.[16] By 2005, it was estimated to be in use on over half of theLinux market,[3] and by 2007 YUM was considered the "tool of choice" for RPM-based Linux distributions.[17]
YUM aimed to address both the perceived deficiencies in the oldAPT-RPM,[18] and restrictions of the Red Hatup2date package management tool. YUM superseded up2date in Red Hat Enterprise Linux 5 and later.[19] Some authors refer to YUM as the Yellowdog Update Manager, or suggest that "Your Update Manager" would be more appropriate.[20][21] A basic knowledge of YUM is often included as a requirement for Linux system-administrator certification.[5] TheGNU General Public License of YUM allows thefree and open-source software to be freely distributed and modified without any royalty, if other terms of the license are honored.[4]
While yum was originally created for Linux, it has been ported to a number of other operating systems includingAIX,[22]IBM i,[23] andArcaOS.[24]
![[icon]](/mt/?noimg=&dark=on&url=http%3a%2f%2fen.wikipedia.org%2fwiki%2fFile%3aWiki_letter_w_cropped.svg) | This sectionneeds expansion. You can help byadding to it.(August 2014) |
YUM can perform operations such as:
yum install <package_name>
yum remove <package_name>
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.[26] A commonly installed[27] packageyum-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.[8] 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.[29]
Information about packages (as opposed to the packages themselves) is known asmetadata. 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 asdependency hell. A separate tool,createrepo, sets up YUMsoftware repositories, generating the necessary metadata in a standardXML format (and theSQLite metadata if given the -d option).[30][31] Themrepo tool (formerly known as Yam) can help in the creation and maintenance of repositories.[32]
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[33] added support for YUM repositories inYaST, and theOpen Build Service repositories use the YUM XML repository format metadata.[31]
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.[34][35]
| dpkg | |
|---|---|
| RPM | |
| Embedded systems |
|
| Distribution-agnostic | |
| Others (binary) | |
| Others (source) | |
| Front-ends | |
| Related topics | |
Italics= inactive or discontinued | |
