rpm

Use the database in DIRECTORY rathen than the default path /var/lib/rpm

Print a longer usage message then normal.

Pipes the output of rpm to the command CMD.

Print as little as possible - normally only error messages will be displayed.

Each of the files in the colon separated FILELIST is read sequentially by rpm for configuration information. Only the first file in the list must exist, and tildes will be expanded to the value of $HOME. The default FILELIST is /usr/lib/rpm/rpmrc:/etc/rpmrc:~/.rpmrc.

Use the system rooted at DIRECTORY for all operations. Note that this means the database will be read or modified under DIRECTORY and any %pre or %post scriptlet(s) are run after a chroot(2) to DIRECTORY.

Print a single line containing the version number of rpm being used.

Print lots of ugly debugging information.

Installs or upgrades all the missingok files in the package, regardless if they exist.

Used with --relocate, permit relocations on all file paths, not just those OLDPATH's included in the binary package relocation hint(s).

Don't install files whose name begins with OLDPATH.

Don't install any files which are marked as documentation (which includes man pages and texinfo documents).

Same as using --replacepkgs, --replacefiles, and --oldpackage.

Print 50 hash marks as the package archive is unpacked. Use with -v | --verbose for a nicer display.

Don't check mount file systems for sufficient disk space before installing this package.

Allow installation or upgrading even if the architectures of the binary package and host don't match.

Allow installation or upgrading even if the operating systems of the binary package and host don't match.

Install documentation files. This is the default behavior.

Update only the database, not the filesystem.

Don't do a dependency check before installing or upgrading a package.

Don't reorder the packages for an install. The list of packages would normally be reordered to satisfy dependancies.

Don't execute the %pre or %post scriptlet(s).

Don't execute scripts which are triggered by the installation of this package.

Allow an upgrade to replace a newer package with an older one.

Print percentages as files are unpacked from the package archive. This is intended to make rpm easy to run from other tools.

For relocateable binary packages, translate all file paths that start with the installation prefix in the package relocation hint(s) to NEWPATH.

For relocatable binary packages, translate all file paths that start with OLDPATH in the package relocation hint(s) to NEWPATH. This option can be used repeatedly if several OLDPATH's in the package are to be relocated.

Install the packages even if they replace files from other, already installed, packages.

Install the packages even if some of them are already installed on this system.

Do not install the package, simply check for and report potential conflicts.

Query installed package named PACKAGE_NAME.

Query all installed packages

Query package owning FILE.

Query packages with the group of GROUP.

Query an (uninstalled) package URLFILE. The URLFILE may be specified as an ftp or http style URL, in which case the package header will be downloaded and queried. See FTP/HTTP OPTIONS for information on rpm's internal ftp and http client support. The URLFILE argument(s), if not a binary package, will be interpreted as an ASCII package manifest. Comments are permitted, starting with a '#', and each line of a package manifest file may include white space seperated glob expressions, including URL's with remote glob expressions, that will be expanded to paths that are substituted in place of the package manifest as additional URLFILE arguments to the query.

Query the NUMBERth database entry directly; this is helpful for debugging purposes.

Parse and query SPECFILE as if it were a package. Although not all the information (e.g. file lists) is available, this type of query permits rpm to be used to extract information from spec files without having to write a specfile parser.

Query packages that are triggered by package(s) PACKAGE_NAME.

Query all packages that provide the CAPABILITY capability.

Query all packages that requires CAPABILITY for proper functioning.

Display change information for the package.

List only configuration files (implies -l).

List only documentation files (implies -l).

Dump file information as follows: path size mtime md5sum mode owner group isconfig isdoc rdev symlink. This must be used with at least one of -l, -c, -d.

This lists all the files in each package.

Display package information, including name, version, and description. This uses the --queryformat if one was specified.

Orders the package listing by install time such that the latest packages are at the top.

List files in package.

List capabilities this package provides.

List packages on which this package depends.

List the package specific scriptlet(s) that are used as part of the installation and uninstallation processes.

Display the states of files in the package (implies -l). The state of each file is one of normal, not installed, or replaced.

Display the trigger scripts, if any, which are contained in the package.

Don't verify dependencies.

Don't verify files.

Don't verify file MD5 checksums.

Don't execute the %verifyscript scriptlet (if any).

Remove all versions of the package which match PACKAGE_NAME. Normally an error is issued if PACKAGE_NAME matches multiple packages.

Don't check dependencies before uninstalling the packages.

Don't execute the %preun, or %postun scriptlet(s).

Don't execute scripts which are triggered by the removal of this package.

Don't really uninstall anything, just go through the motions. Useful in conjunction with the -vv option.

Executes the "%prep" stage from the spec file. Normally this involves unpacking the sources and applying any patches.

Do a "list check". The "%files" section from the spec file is macro expanded, and checks are made to verify that each file exists.

Do the "%build" stage from the spec file (after doing the %prep stage). This generally involves the equivalent of a "make".

Do the "%install" stage from the spec file (after doing the %prep and %build stages). This generally involves the equivalent of a "make install".

Build a binary package (after doing the %prep, %build, and %install stages).

Build just the source package.

Build binary and source packages (after doing the %prep, %build, and %install stages).

When building a package, override the BuildRoot tag with directory DIRECTORY.

Remove the build tree after the packages are made.

Remove the sources after the build (may also be used standalone, e.g. "rpm --rmsource foo.spec").

Remove the spec file after the build (may also be used standalone, eg. "rpm --rmspec foo.spec").

Skip straight to specified stage (i.e., skip all stages leading up to the specified stage). Only valid with -bc and -bi.

Embed a PGP signature in the package. This signature can be used to verify the integrity and the origin of the package. See the section on PGP SIGNATURES for configuration details.

When building the package, interpret PLATFORM as arch-vendor-os and set the macros %_target, %_target_arch, and %_target_os accordingly.

Do not execute any build stages. Useful for testing out spec files.

The signature type. Right now only pgp is supported.

The name of the "user" whose key you wish to use to sign your packages.

The host HOST will be used as a proxy server for all ftp transfers, which allows users to ftp through firewall machines which use proxy systems. This option may also be specified by configuring the macro %_ftpproxy.

The TCP PORT number to use for the ftp connection on the proxy ftp server instead of the default port. This option may also be specified by configuring the macro %_ftpport.

The host HOST will be used as a proxy server for all http transfers. This option may also be specified by configuring the macro %_httpproxy.

The TCP PORT number to use for the http connection on the proxy http server instead of the default port. This option may also be specified by configuring the macro %_httpport.