Книга: Fedora™ Unleashed, 2008 edition
Two Handy Options
Two Handy Options
By appending v
or h
to any option, you get the following:
? v
— Some status feedback
? h
— Hash marks as the work proceeds
Many additional options can also be added to or used in conjunction with these options. Table 34.1 summarizes these.
TABLE 34.1 Handy Options to Use with rpm
Option | Used To |
---|---|
rpm-i |
Install a package Useful options to -i : |
--excludedocs : Does not install documentation to save space |
|
--replacepkgs : Replaces the package with a new copy of itself |
|
--force : The "big hammer" — Ignores all warnings and installs anyway |
|
--noscripts : Does not execute any pre- or post-install scripts |
|
--nodeps : Ignores any dependencies |
|
--root path : Sets an alternative root to path |
|
rpm -e |
Erase (deletes) a package. Useful option to -e : |
--nodeps : Ignores any dependencies |
|
rpm -U |
Upgrade a package, removing the older one but keeping modified files, such as configurations. Useful options to -U : |
--oldpackage : Permits downgrading to an older version |
|
Other options are the same as with rpm -i |
|
rpm -q |
Query about package information. Useful options to -q : |
-p file : Displays all information about the package file |
|
-f file : Asks what package owns the file file? |
|
--whatprovides x : Determines what packages provide x |
|
--whatrequires x: Determines what packages require x |
|
-i : Summarizes the package information |
|
-l : Lists the files in package |
|
--scripts : Displays the contents of any install, uninstall, or verifies scripts |
|
--provides : Displays the capabilities package provides |
|
--requires : Displays the capabilities package requires |
|
rpm -V |
Verify packages against the RPM database .Useful options to -V : |
-a : Verifies all installed packages |
|
rpm -K |
Use GPG to verify a downloaded package Useful options to -K : |
--nosignature : If you lack public GPG encryption keys, do not have GPG installed, or are legally prohibited from using GPG, this still verifies the package using size and MD5 checksums. |
RPM Is for Programmers, Too!
Remember that RPM was created not only to provide an easy-to-use administrative tool, but also as a developer's tool for use in multiplatform source-code package management. Programmers using rpm
for development and distribution use its rpmbuild
command, along with a myriad of additional command-line flags. RPM can be used to build binaries, execute programs, test installations, verify and sign packages, build source packages, track versions, and target builds for specific architectures. You can find details at the RPM home page (http://www.rpm.org).