RPM manual

--Dbpath

Use RPM's database in accordance with .

--justdb

Update only for the database instead of the entire file system.

- FTPPROXY , - httpproxy

Set a proxy server for FTP or HTTP. See the FTP / HTTP option.

- FTPPORT , --httpport

Set The port of the proxy server for FTP or HTTP. See the FTP / HTTP option.

--PIPE

Enter the output of the RPM to the command by the pipeline. Install and upgrade options

The usual rpm installation command is as follows:

RPM -I [Install-Options]

This will install a new package. The usual RPM upgrade command is as follows:

RPM -U [Install-Options]

This will install the currently installed package upgrade or newly installed RPM version. Upgrade and installation are the same, the difference is that the upgrade wants to remove all other versions of the package from the system.

RPM [-f | --freshen] [install-options]

This is also upgraded, but only this way is used when there is an earlier version of the system.

If you want to download before installation, should be specified as an FTP or HTTP URL. To get information about the FTP and HTTP support supported by the RPM package,

You can refer to the FTP / HTTP option.

--force

With the use -ReplacePkgs, - ReplaceFiles, and - LLDPackage effects

-H, --hash

If the package is not unbealed, print 50 broken numbers. Match -V use can make it better show.

--OLDPACKAGE

Allows replace newers with older versions.

--Percent

Give the file from the percentage of the package unpacking. The role of this is to make RPM more easily than other tools.

--ReplaceFiles

Even if you want to install the package to replace the files of other installed packets, the package is also installed.

--ReplacePkgs

Even if the part of the package is installed in the system, the package is also installed.

--allfiles

Install or upgrade all the missing files in the package, regardless of whether it is present.

--Nodeps

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

--Noscripts

No script before installation or after installation

--Notriggers

No scripts excited by the installation of the package

--IgnoreSize

Do not check if the mount file system has enough disk space before installing the package.

--Excludepath

Do not install file names with files starting with path .

--excludedocs

Do not install any files marked as documentation (including man page and text information file).

- Includedocs

Install the document file, this is the default operation.

--Test

No package, just simply check and report possible conflicts.

--Ignorearch

Allows the installation or upgrade its system with the binary RPM package that does not match the host.

--Ignoreos

Allow installation or upgrade its operating system with a binary RPM package that does not match the host.

--Prefix

For a float package, this will set the installation prefix to .

--Relocate =

Change the file from to , which makes it possible to float.

--badreloc

Used with -relocate, forcibly modify the unfunctuous package.

--Noorder

When installing, the package is not reordered, and the package list should be re-sorted when installing to meet dependence.

Query option

The RPM query command usually format is as follows:

RPM -Q [Query-Options]

You can make a print format of the package information, then use the [--queryformat | -qf] option, the format string follows the option.

The query format is determined by the version of the standard printf (3) format. The format is static string (including standard C characters other than newline characters, Tab, and other special characters),

And Printf (3) type format. If rpm already knows the print type, the type description must be ignored, and replaced with the name of the head TAG to be printed, the name is enclosed in

Between {}. And the RPMTAG_ section of the TAG is also ignored.

You can use: TypetAg to change the output format. Currently supports with the following types: Octal, Date, Shescape, Perms, Fflags, and DEPFLAGS. For example, to print the name of the query package, you can use% {Name} as a format string To print the package and distribution information in both columns, you can use% -30 {name}% {distribution}.

RPM will list all tags when the QueryTags parameter is excited.

The query option has two sub-settings: package selection and information selection.

Package selection option:

Query the installation package named .

-a, --all

Query all installed packages.

--WhatRequires

Query all packages that need to provide appropriate features.

--WhatProvides

Query all packages that provide feature.

-f , --file

Query the package with file .

-g , --Group

The query belongs to ??? group package

-p

Query a package . can be explained as an FTP or HTTP URL, then the header will be downloaded and queried. To get about RPM

For information on FTP and HTTP clients, see FTP / HTTP OPTIONS

--Specfile

Like a package, the same PARSE and query . Although not all information (such as a list of files) is available, this query type allows RPM to write a specfile

Parser is extracted from the SPEC Files.

- QueryBynumber

Query the database portfolio directly, which is useful in debugging.

--TriggeredBy

The query is made by the package of .

Information Selection Options:

-i

Display package information, including name, version, and description.???

-R, --Requires

List other packages dependent on the package.

--Provides

List the functions provided by the package.

--changelog

Display the change information of the package.

-L, --List

List the files of the package.

-S, --State

Show the status information of each file of the package, so this option is actually implied. The file status can be one of the following: Normal, Not Installed, or Replaced.

-d, - Docfiles

Only document files (implicit -l option) are listed.

-c, --configfiles

Only the configuration file (implicit -l option) is listed.

--Scripts

If any, the special shell script is listed as part of the installation or uninstall process.

--Triggers, --Triggerscripts

If there is, the excitation script containing the package is displayed.

-dump

Duggle file information as follows: Path Size Mtime Md5Sum Mode Owner Group Isconfig Isdoc RDEV SYMLINK. This option must be at least one of the following options.

: -l, -c, -d.

--last

Sort by the installation time of the package, which makes the latest package on the top of the sequence.

--querybypkg

List all files in each package.

--Triggerscripts

Display all excitation scripts of the selected package.

Verify

Rpm -v | -y | --verify [verify-options]]

Compare the file information of the package and the file information of the source package and the file information of the RPM database to verify the package. For other things, then any differences

Will display. The instructions for the package are the same as the query option.

For documents that are not from the package installed, for example, in the installation of the document file, the document file is excluded from the "--exCludedocs" option will be ignored without the prompt. The verification option can be used as the following mode:

--nofiles

Ignore the missing file when verified

--nomd5

Ignore the MD5 check error when verifying

--NOPGP

Ignore the PGP check error when verifying

--nofiles

Ignore the missing file when verified

The output format is a string of eight characters, and a possible "C", indicating that the following is a configuration file, as well as the following file name. Each of the eight characters representative

A comparison result for a file attribute with the properties record value saved in the RPM database. Single "." (Period) indicates that the check is passed. The following characters represent the failure of a specific check:

5

MD5 checksum

S

File size

L

Symbolic connection

T

Change the time

Di

equipment

U

user

G

group

M

Mode (including license and file type)

Signature check

The usual RPM signature check command is as follows:

RPM --Checksig

This will check the PGP signature of the package to ensure its integrity and source. You can read the PGP configuration information from the configuration file. Details please check the PGP signature section.

Uninstall option

The usual format of the RPM uninstall command is as follows:

RPM -E

- AlLmatches

The packets that are mounted with . Normally, if matches multiple packages, the error message will be given.

--Noscripts

Do not perform the installation or post-installation script.

--Notriggers

Do not perform scripts caused by removing the package

--Nodeps

Do not check dependencies before uninstallation

--Test

Don't really uninstall anything, just traverse this action. It works with the -vv option.

Election option

The General Form of an RPM Build Command IS

RPM - [B | T] o [Build-Options]

The argument use is -b if a spec file is being used to build the package and -t if rpm shouth ins

Gzipped (or compressed) Tar File for the spec file to use. after the first argument, The next argument (o) Specifies

The Stages Of Building and Packaging to Be Done and is one of: RPM usually generated options:

RPM - [B | T] o [Build-Options]

-bp

EXECUTES The "% Prep" stage from the spec file. Normally this involves unpacking the source and applying any patches.

-bl

Do a "List Check". The "% files" section from the spec file is macro expanded, and checks are master to verify That Each

File exisss.

-BC

Do The "% Build" stage from the spec file (after doing the preput). This Generally Involves The Equivalent of A

"Make".

-bi

Do The "% Install" Stage from The Spec File (After Doying The Prep and Build Stages). This Generally Involves theequivalent of a "make install".

-BB

Generate a binary package (after completing the pred, build, and the install phase)

-BS

Only generate a source package (after completing pre-preme, after the install phase)

-bA

Generate binary bags and source packages (after completing preP, build, and the install phase)

The options you can use are as follows:

--Short-Circuit

Ignore the Specified phase (for example, ignoring all the phases that cause the specified phase). Only the -bc and -bi are only valid.

--TimeCheck

Set the value of "timeCheck" (0-?). This value can also be configured by defining the macro "_timecheck". The timeCheck value is in seconds, indicating a maximum age of a package generation. If

The time exceeds this value, the warning information is given to all files.

--clean

After the package is completed, remove the spanning tree.

--RMSource

After the generation of the package is completed, the source and the SPEC file (can also be used alone, such as "rpm --rmsource foo.spec").

--Test

No generated phase is not performed. It is useful when testing the SPEC file.

- Sign

Embed a PGP signature in the package. This signature can be used to verify the integrity and source of the package. The configuration details can be checked in the PGP signature section.

--BUILDROOT