Recipe 2.2. Installing RPMs

2.2.1 Problem

You need to know how to install software packages on Red Hat and Red Hat-type systems.

2.2.2 Solution

Use RPM, the Package Manager. Red Hat installation command syntax looks like this:

# rpm -i packagename

For example, the following command installs the drawing program Tuxpaint. -v adds verbose feedback, and -h draws progress hashmarks:

# rpm -ivh tuxpaint-9.13-1.i386.rpm Preparing...########################### [100%]    1. tuxpaint ######################## [100%]

To test the installation first, without installing anything, use:

# rpm -ivh  test tuxpaint-9.13-1.i386.rpm Preparing...########################### [100%] #

2.2.3 Discussion

RPM hell, or getting caught in an endless chain of unresolved dependencies, is the most common RPM problem. Here are some ways to prevent it:

• Do not let any dependencies remain unresolved. They don't fix themselves; they lurk and grow larger over time.

• The quality of RPMs varies wildly. Anyone can throw one together and post it for distribution. As much as possible, stick with RPMs built for your distribution and architecture. Polished Linux Distribution (PLD) builds good-quality RPMs for all x86 systems.

• Use CheckInstall when you need a source-built program. CheckInstall creates Red Hat, Debian, and Slackware packages, so you get the benefits of both a custom compilation and your package manager (see Recipe 4.5, Recipe 4.5).

2.2.4 See Also

• rpm(8)

• RPM.org (http://www.rpm.org/)

• Maximum RPM (http://www.rpm.org/max-rpm/index.html)