Yum (software)

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 Kai Staats) as a back-end engine for a graphical installer of Yellow Dog Linux. In 2003 Robert G. Brown at Duke published documentation for YUM. Subsequent adopters included By 2005, it was estimated to be in use on over half of the Linux market, YUM aimed to address both the perceived deficiencies in the old APT-RPM, and restrictions of the Red Hat up2date package management tool. YUM superseded up2date in Red Hat Enterprise Linux 5 and later. Some authors refer to YUM as the Yellowdog Update Manager, or suggest that "Your Update Manager" would be more appropriate. A basic knowledge of YUM is often included as a requirement for Linux system-administrator certification. IBM i, and ArcaOS. == Operations ==

YUM can perform operations such as: • Installing packages yum install • Deleting packages yum remove • updating existing installed packages yum update • listing available packages yum list available • listing installed packages yum list installed == Extensions ==

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. A commonly installed 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. Yum Extender was deprecated for a while when Fedora migrated to DNF, 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. == Metadata ==

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). YUM's XML repository, built with input from many other developers, quickly became the standard for RPM-based repositories. Besides the distributions that use YUM directly, SUSE Linux 10.1 added support for YUM repositories in YaST, and the Open Build Service repositories use the YUM XML repository format metadata. == See also ==