Yummy, yummy, yummy


Most of the time, you can use Yum without any options. A few options, such as --obsoletes, provide useful information to help you administer software installation. A great many more, however, enable or disable information for various purposes.

Some options, such as -d and -e, which set debugging and error-level reporting, are largely for developers. The same is true of -v or --verbose, two equivalent options that increase the amount of information that Yum provides while running.

Other options are for users who want to use Yum with a minimum of fuss, such as --quiet, which causes Yum to run without reporting what it is doing. Its frequent companion is -y, which assumes that the answers to all questions are "Yes" – including the question of whether you want to proceed after Yum finishes its initial calculations. In much the same way, --nogpgcheck disables package verification.

Such options save time as well as your own watchfulness. However, I suggest that you avoid them on the general principle that giving up control is rarely a good idea. If nothing else, something as simple as a typing error could start Yum off on a series of actions that could trash your system – or at least require some careful repairs.

Other options are less likely to cause trouble. The matched pair --enable-repo= and disable-repo= give Yum the equivalent of apt-get's pinning and specify which repositories to use. Also, you can use --exclude= to prevent packages that could cause a conflict from installing from any source.

Another option that might keep you out of trouble is --skip-broken. If you use it after Yum reports a missing dependency, it might just allow you to resolve the difficulty. In some cases, the packages installed with this option will not work, but you can make sure that they do not form a bottleneck that keeps Yum from working. Once they are installed, you can then delete them normally.


Yum's commands and options provide all the functionality most users will need. However, if you're looking for something extra, or you want to see what the future of Yum might be, take the time to look at the plugins available for your distribution. Written in Python, Yum plugins are available as separate packages for your distribution, with each plugin adding new features.

By default, plugins are not turned on. Before you can use any of them, you need to open /etc/yum.conf and add or edit the plugins line in the main section of the file to read plugins=1.

In Fedora and Red Hat, some of the most common plugins are available in the yum-utils package. Approximately another 20 plugins are also currently available. Their functionality covers almost everything you can imagine and is too much to describe in detail here.

Briefly, though, some useful Yum plugins in Fedora 11 are:

  • yum-plugin-version-lock: Prevents a particular version of a program from being overwritten.
  • yum-plugin-protects-packages: Prevents designated packages (including Yum) from being removed.
  • yum-plugin-allowdowngrades: Allows you to downgrade a package – an operation that is needed sometimes for compatibility between packages.
  • yum-plugin-fastest-mirror: Lists the fastest mirrors for the repositories you request.
  • yum-presto: Instructs Yum to look for DeltaRPMs rather than straight RPMs. DeltaRPMs are packages that include only changes in a package, so by using them, you can install a package faster and with less bandwidth.
  • yum-plugin-security: Adds options to limit upgrades to those for security.

Many, if not all, plugins work automatically, so they do not include any man pages or help. However, you can see which plugins are installed on your system with the command yum search yum.

Very occasionally, you might find that a plugin, or perhaps a conflict between two or more plugins, prevents Yum from working properly. If that happens, you can use the option --disableplugin= [plugin name] to help you troubleshoot by disabling a specific plugin. If you are in serious difficulties, you can use the option --noplugins to run Yum without any plugins so that, with any luck, you can recover.

Other Package Managers

Yum is not the only RPM-based package manager available. Mandriva uses a similar tool called urpmi, and openSUSE uses Smart, a manager that not only resembles Yum but can install from Yum repositories. Other package management systems include Gentoo's Portage and Conary, which include version control that allows you to install different releases of the same packages.

However, Yum is almost certainly the most commonly used package manager after Debian and Ubuntu's apt-get. Furthermore, because Yum was developed years after apt-get, its developers had the chance to learn from apt-get and improve on it.

Although you probably won't see much in Yum that isn't in apt-get and its related utilities, you will find a less haphazard organization. In fact, if you know apt-get and are encountering Yum for the first time, you will likely be struck by how structured Yum is and how much easier it is to learn than apt-get. As a program, Yum is an intelligent innovation – and as a remedy for dependency hell, nothing short of a godsend.

Buy Linux Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Yum

    The RPM package manager Yum has its own advantages over other tools.

  • Command Line: Apt-get

    Dependency tangles fall away with the Debian package system.

  • Command Line – Package Management

    When human error stumps the Debian package manager, familiar tools like apt-get, aptitude, and dpkg can help restore functionality.

  • Command Line: Vim Plugins

    Managing plugins is a requirement for Vim users, and plugin managers can make the task easier. We look at four options.

  • apt vs. apt-get

    The apt command-line utility is a successor to the well known apt-get, offering simpler installation and maintenance for the DEB packages used with Debian, Ubuntu, Knoppix, and many other Linux distros.

comments powered by Disqus

Direct Download

Read full article as PDF: