1RPM(8) Red Hat Linux RPM(8)
2
6 rpm - RPM Package Manager
7
9 QUERYING AND VERIFYING PACKAGES:
10 rpm {-q|--query} [select-options] [query-options]
11 rpm {-V|--verify} [select-options] [verify-options]
15 rpm --import PUBKEY ...
19 rpm {-K|--checksig} [--nosignature] [--nodigest]
23 PACKAGE_FILE ...
24 INSTALLING, UPGRADING, AND REMOVING PACKAGES:
27 rpm {-i|--install} [install-options] PACKAGE_FILE ...
28 rpm {-U|--upgrade} [install-options] PACKAGE_FILE ...
32 rpm {-F|--freshen} [install-options] PACKAGE_FILE ...
36 rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts]
40 [--notriggers] [--repackage] [--test] PACKAGE_NAME ...
41 MISCELLANEOUS:
44 rpm {--initdb|--rebuilddb}
45 rpm {--addsign|--resign} PACKAGE_FILE ...
49 rpm {--querytags|--showrc}
53 rpm {--setperms|--setugids} PACKAGE_NAME ...
57 select-options
60 [PACKAGE_NAME] [-a,--all] [-f,--file FILE]
61 [-g,--group GROUP] {-p,--package PACKAGE_FILE]
62 [--fileid MD5] [--hdrid SHA1] [--pkgid MD5] [--tid TID]
63 [--querybynumber HDRNUM] [--triggeredby PACKAGE_NAME]
64 [--whatprovides CAPABILITY] [--whatrequires CAPABILITY]
65 query-options
68 [--changelog] [-c,--configfiles] [-d,--docfiles] [--dump]
69 [--filesbypkg] [-i,--info] [--last] [-l,--list]
70 [--provides] [--qf,--queryformat QUERYFMT]
71 [-R,--requires] [--scripts] [-s,--state]
72 [--triggers,--triggerscripts]
73 verify-options
76 [--nodeps] [--nofiles] [--noscripts]
77 [--nodigest] [--nosignature]
78 [--nolinkto] [--nomd5] [--nosize] [--nouser]
79 [--nogroup] [--nomtime] [--nomode] [--nordev]
80 install-options
83 [--aid] [--allfiles] [--badreloc] [--excludepath OLDPATH]
84 [--excludedocs] [--force] [-h,--hash]
85 [--ignoresize] [--ignorearch] [--ignoreos]
86 [--includedocs] [--justdb] [--nodeps]
87 [--nodigest] [--nosignature] [--nosuggest]
88 [--noorder] [--noscripts] [--notriggers]
89 [--oldpackage] [--percent] [--prefix NEWPATH]
90 [--relocate OLDPATH=NEWPATH]
91 [--repackage] [--replacefiles] [--replacepkgs]
92 [--test]
93
96 rpm is a powerful Package Manager, which can be used to build, install,
97 query, verify, update, and erase individual software packages. A pack‐
98 age consists of an archive of files and meta-data used to install and
99 erase the archive files. The meta-data includes helper scripts, file
100 attributes, and descriptive information about the package. Packages
101 come in two varieties: binary packages, used to encapsulate software to
102 be installed, and source packages, containing the source code and
103 recipe necessary to produce binary packages.
104 One of the following basic modes must be selected: Query, Verify, Sig‐
106 nature Check, Install/Upgrade/Freshen, Uninstall, Initialize Database,
107 Rebuild Database, Resign, Add Signature, Set Owners/Groups, Show Query‐
108 tags, and Show Configuration.
109 GENERAL OPTIONS
111 These options can be used in all the different modes.
112 -?, --help
114 Print a longer usage message then normal.
115 --version
117 Print a single line containing the version number of rpm being
118 used.
119 --quiet
121 Print as little as possible - normally only error messages will
122 be displayed.
123 -v Print verbose information - normally routine progress messages
125 will be displayed.
126 -vv Print lots of ugly debugging information.
128 --rcfile FILELIST
130 Each of the files in the colon separated FILELIST is read
131 sequentially by rpm for configuration information. Only the
132 first file in the list must exist, and tildes will be expanded
133 to the value of $HOME. The default FILELIST is
134 /usr/lib/rpm/rpmrc:/usr/lib/rpm/red‐
135 hat/rpmrc:/etc/rpmrc:~/.rpmrc.
136 --pipe CMD
138 Pipes the output of rpm to the command CMD.
139 --dbpath DIRECTORY
141 Use the database in DIRECTORY rather than the default path
142 /var/lib/rpm
143 --root DIRECTORY
145 Use the file system tree rooted at DIRECTORY for all operations.
146 Note that this means the database within DIRECTORY will be used
147 for dependency checks and any scriptlet(s) (e.g. %post if
148 installing, or %prep if building, a package) will be run after a
149 chroot(2) to DIRECTORY.
150 INSTALL AND UPGRADE OPTIONS
152 The general form of an rpm install command is
153 rpm {-i|--install} [install-options] PACKAGE_FILE ...
155 This installs a new package.
158 The general form of an rpm upgrade command is
160 rpm {-U|--upgrade} [install-options] PACKAGE_FILE ...
162 This upgrades or installs the package currently installed to a newer
165 version. This is the same as install, except all other version(s) of
166 the package are removed after the new package is installed.
167 rpm {-F|--freshen} [install-options] PACKAGE_FILE ...
169 This will upgrade packages, but only if an earlier version currently
172 exists. The PACKAGE_FILE may be specified as an ftp or http URL, in
173 which case the package will be downloaded before being installed. See
174 FTP/HTTP OPTIONS for information on rpm's internal ftp and http client
175 support.
176 --aid Add suggested packages to the transaction set when needed.
178 --allfiles
180 Installs or upgrades all the missingok files in the package,
181 regardless if they exist.
182 --badreloc
184 Used with --relocate, permit relocations on all file paths, not
185 just those OLDPATH's included in the binary package relocation
186 hint(s).
187 --excludepath OLDPATH
189 Don't install files whose name begins with OLDPATH.
190 --excludedocs
192 Don't install any files which are marked as documentation (which
193 includes man pages and texinfo documents).
194 --force
196 Same as using --replacepkgs, --replacefiles, and --oldpackage.
197 -h, --hash
199 Print 50 hash marks as the package archive is unpacked. Use
200 with -v|--verbose for a nicer display.
201 --ignoresize
203 Don't check mount file systems for sufficient disk space before
204 installing this package.
205 --ignorearch
207 Allow installation or upgrading even if the architectures of the
208 binary package and host don't match.
209 --ignoreos
211 Allow installation or upgrading even if the operating systems of
212 the binary package and host don't match.
213 --includedocs
215 Install documentation files. This is the default behavior.
216 --justdb
218 Update only the database, not the filesystem.
219 --nodigest
221 Don't verify package or header digests when reading.
222 --nosignature
224 Don't verify package or header signatures when reading.
225 --nodeps
227 Don't do a dependency check before installing or upgrading a
228 package.
229 --nosuggest
231 Don't suggest package(s) that provide a missing dependency.
232 --noorder
234 Don't reorder the packages for an install. The list of packages
235 would normally be reordered to satisfy dependencies.
236 --noscripts
238 --nopre
240 --nopost
242 --nopreun
244 --nopostun
246 Don't execute the scriptlet of the same name. The --noscripts
247 option is equivalent to
248 --nopre --nopost --nopreun --nopostun
250 and turns off the execution of the corresponding %pre, %post,
252 %preun, and %postun scriptlet(s).
253 --notriggers
255 --notriggerin
257 --notriggerun
259 --notriggerpostun
261 Don't execute any trigger scriptlet of the named type. The
262 --notriggers option is equivalent to
263 --notriggerin --notriggerun --notriggerpostun
265 and turns off execution of the corresponding %triggerin, %trig‐
267 gerun, and %triggerpostun scriptlet(s).
268 --oldpackage
270 Allow an upgrade to replace a newer package with an older one.
271 --percent
273 Print percentages as files are unpacked from the package ar‐
274 chive. This is intended to make rpm easy to run from other
275 tools.
276 --prefix NEWPATH
278 For relocatable binary packages, translate all file paths that
279 start with the installation prefix in the package relocation
280 hint(s) to NEWPATH.
281 --relocate OLDPATH=NEWPATH
283 For relocatable binary packages, translate all file paths that
284 start with OLDPATH in the package relocation hint(s) to NEWPATH.
285 This option can be used repeatedly if several OLDPATH's in the
286 package are to be relocated.
287 --repackage
289 Re-package the files before erasing. The previously installed
290 package will be named according to the macro %_repack‐
291 age_name_fmt and will be created in the directory named by the
292 macro %_repackage_dir (default value is /var/spool/repackage).
293 --replacefiles
295 Install the packages even if they replace files from other,
296 already installed, packages.
297 --replacepkgs
299 Install the packages even if some of them are already installed
300 on this system.
301 --test Do not install the package, simply check for and report poten‐
303 tial conflicts.
304 ERASE OPTIONS
306 The general form of an rpm erase command is
307 rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts] [--notriggers]
309 [--repackage] [--test] PACKAGE_NAME ...
310 The following options may also be used:
313 --allmatches
315 Remove all versions of the package which match PACKAGE_NAME.
316 Normally an error is issued if PACKAGE_NAME matches multiple
317 packages.
318 --nodeps
320 Don't check dependencies before uninstalling the packages.
321 --noscripts
323 --nopreun
325 --nopostun
327 Don't execute the scriptlet of the same name. The --noscripts
328 option during package erase is equivalent to
329 --nopreun --nopostun
331 and turns off the execution of the corresponding %preun, and
333 %postun scriptlet(s).
334 --notriggers
336 --notriggerun
338 --notriggerpostun
340 Don't execute any trigger scriptlet of the named type. The
341 --notriggers option is equivalent to
342 --notriggerun --notriggerpostun
344 and turns off execution of the corresponding %triggerun, and
346 %triggerpostun scriptlet(s).
347 --repackage
349 Re-package the files before erasing. The previously installed
350 package will be named according to the macro %_repack‐
351 age_name_fmt and will be created in the directory named by the
352 macro %_repackage_dir (default value is /var/spool/repackage).
353 --test Don't really uninstall anything, just go through the motions.
355 Useful in conjunction with the -vv option for debugging.
356 QUERY OPTIONS
358 The general form of an rpm query command is
359 rpm {-q|--query} [select-options] [query-options]
361 You may specify the format that package information should be printed
364 in. To do this, you use the
365 --qf|--queryformat QUERYFMT
367 option, followed by the QUERYFMT format string. Query formats are mod‐
369 ified versions of the standard printf(3) formatting. The format is made
370 up of static strings (which may include standard C character escapes
371 for newlines, tabs, and other special characters) and printf(3) type
372 formatters. As rpm already knows the type to print, the type specifier
373 must be omitted however, and replaced by the name of the header tag to
374 be printed, enclosed by {} characters. Tag names are case insensitive,
375 and the leading RPMTAG_ portion of the tag name may be omitted as well.
376 Alternate output formats may be requested by following the tag with
378 :typetag. Currently, the following types are supported:
379 :armor
381 Wrap a public key in ASCII armor.
383 :base64
385 Encode binary data using base64.
386 :date Use strftime(3) "%c" format.
388 :day Use strftime(3) "%a %b %d %Y" format.
390 :depflags
392 Format dependency flags.
393 :fflags
395 Format file flags.
396 :hex Format in hexadecimal.
398 :octal Format in octal.
400 :perms Format file permissions.
402 :shescape
404 Escape single quotes for use in a script.
405 :triggertype
407 Display trigger suffix.
408 For example, to print only the names of the packages queried, you could
410 use %{NAME} as the format string. To print the packages name and dis‐
411 tribution information in two columns, you could use %-30{NAME}%{DISTRI‐
412 BUTION}. rpm will print a list of all of the tags it knows about when
413 it is invoked with the --querytags argument.
414 There are two subsets of options for querying: package selection, and
416 information selection.
417 PACKAGE SELECTION OPTIONS:
419 PACKAGE_NAME
420 Query installed package named PACKAGE_NAME.
421 -a, --all
423 Query all installed packages.
424 -f, --file FILE
426 Query package owning FILE.
427 --fileid MD5
429 Query package that contains a given file identifier, i.e. the
430 MD5 digest of the file contents.
431 -g, --group GROUP
433 Query packages with the group of GROUP.
434 --hdrid SHA1
436 Query package that contains a given header identifier, i.e. the
437 SHA1 digest of the immutable header region.
438 -p, --package PACKAGE_FILE
440 Query an (uninstalled) package PACKAGE_FILE. The PACKAGE_FILE
441 may be specified as an ftp or http style URL, in which case the
442 package header will be downloaded and queried. See FTP/HTTP
443 OPTIONS for information on rpm's internal ftp and http client
444 support. The PACKAGE_FILE argument(s), if not a binary package,
445 will be interpreted as an ASCII package manifest. Comments are
446 permitted, starting with a '#', and each line of a package mani‐
447 fest file may include white space separated glob expressions,
448 including URL's with remote glob expressions, that will be
449 expanded to paths that are substituted in place of the package
450 manifest as additional PACKAGE_FILE arguments to the query.
451 --pkgid MD5
453 Query package that contains a given package identifier, i.e. the
454 MD5 digest of the combined header and payload contents.
455 --querybynumber HDRNUM
457 Query the HDRNUMth database entry directly; this is useful only
458 for debugging.
459 --specfile SPECFILE
461 Parse and query SPECFILE as if it were a package. Although not
462 all the information (e.g. file lists) is available, this type of
463 query permits rpm to be used to extract information from spec
464 files without having to write a specfile parser.
465 --tid TID
467 Query package(s) that have a given TID transaction identifier. A
468 unix time stamp is currently used as a transaction identifier.
469 All package(s) installed or erased within a single transaction
470 have a common identifier.
471 --triggeredby PACKAGE_NAME
473 Query packages that are triggered by package(s) PACKAGE_NAME.
474 --whatprovides CAPABILITY
476 Query all packages that provide the CAPABILITY capability.
477 --whatrequires CAPABILITY
479 Query all packages that requires CAPABILITY for proper function‐
480 ing.
481 PACKAGE QUERY OPTIONS:
483 --changelog
484 Display change information for the package.
485 -c, --configfiles
487 List only configuration files (implies -l).
488 -d, --docfiles
490 List only documentation files (implies -l).
491 --dump Dump file information as follows (implies -l):
493 path size mtime md5sum mode owner group isconfig isdoc rdev symlink
496 --filesbypkg
499 List all the files in each selected package.
500 -i, --info
502 Display package information, including name, version, and
503 description. This uses the --queryformat if one was specified.
504 --last Orders the package listing by install time such that the latest
506 packages are at the top.
507 -l, --list
509 List files in package.
510 --provides
512 List capabilities this package provides.
513 -R, --requires
515 List packages on which this package depends.
516 --scripts
518 List the package specific scriptlet(s) that are used as part of
519 the installation and uninstallation processes.
520 -s, --state
522 Display the states of files in the package (implies -l). The
523 state of each file is one of normal, not installed, or replaced.
524 --triggers, --triggerscripts
526 Display the trigger scripts, if any, which are contained in the
527 package.
528 VERIFY OPTIONS
530 The general form of an rpm verify command is
531 rpm {-V|--verify} [select-options] [verify-options]
533 Verifying a package compares information about the installed files in
536 the package with information about the files taken from the package
537 metadata stored in the rpm database. Among other things, verifying
538 compares the size, MD5 sum, permissions, type, owner and group of each
539 file. Any discrepancies are displayed. Files that were not installed
540 from the package, for example, documentation files excluded on instal‐
541 lation using the "--excludedocs" option, will be silently ignored.
542 The package selection options are the same as for package querying
544 (including package manifest files as arguments). Other options unique
545 to verify mode are:
546 --nodeps
548 Don't verify dependencies of packages.
549 --nodigest
551 Don't verify package or header digests when reading.
552 --nofiles
554 Don't verify any attributes of package files.
555 --noscripts
557 Don't execute the %verifyscript scriptlet (if any).
558 --nosignature
560 Don't verify package or header signatures when reading.
561 --nolinkto
563 --nomd5
565 --nosize
567 --nouser
569 --nogroup
571 --nomtime
573 --nomode
575 --nordev
577 Don't verify the corresponding file attribute.
578 The format of the output is a string of 8 characters, a possible
580 attribute marker:
581 c %config configuration file.
583 d %doc documentation file.
584 g %ghost file (i.e. the file contents are not included in the package payload).
585 l %license license file.
586 r %readme readme file.
587 from the package header, followed by the file name. Each of the 8
589 characters denotes the result of a comparison of attribute(s) of the
590 file to the value of those attribute(s) recorded in the database. A
591 single "." (period) means the test passed, while a single "?" (question
592 mark) indicates the test could not be performed (e.g. file permissions
593 prevent reading). Otherwise, the (mnemonically emBoldened) character
594 denotes failure of the corresponding --verify test:
595 S file Size differs
597 M Mode differs (includes permissions and file type)
598 5 MD5 sum differs
599 D Device major/minor number mismatch
600 L readL[22mink(2) path mismatch
601 U User ownership differs
602 G Group ownership differs
603 T mTime differs
604 DIGITAL SIGNATURE AND DIGEST VERIFICATION
607 The general forms of rpm digital signature commands are
608 rpm --import PUBKEY ...
610 rpm {--checksig} [--nosignature] [--nodigest]
613 PACKAGE_FILE ...
614 The --checksig option checks all the digests and signatures contained
617 in PACKAGE_FILE to ensure the integrity and origin of the package. Note
618 that signatures are now verified whenever a package is read, and
619 --checksig is useful to verify all of the digests and signatures asso‐
620 ciated with a package.
621 Digital signatures cannot be verified without a public key. An ASCII
623 armored public key can be added to the rpm database using --import. An
624 imported public key is carried in a header, and key ring management is
625 performed exactly like package management. For example, all currently
626 imported public keys can be displayed by:
627 rpm -qa gpg-pubkey*
629 Details about a specific public key, when imported, can be displayed by
631 querying. Here's information about the Red Hat GPG/DSA key:
632 rpm -qi gpg-pubkey-db42a60e
634 Finally, public keys can be erased after importing just like packages.
636 Here's how to remove the Red Hat GPG/DSA key
637 rpm -e gpg-pubkey-db42a60e
639 SIGNING A PACKAGE
641 rpm --addsign|--resign PACKAGE_FILE ...
642 Both of the --addsign and --resign options generate and insert new sig‐
645 natures for each package PACKAGE_FILE given, replacing any existing
646 signatures. There are two options for historical reasons, there is no
647 difference in behavior currently.
648 USING GPG TO SIGN PACKAGES
650 In order to sign packages using GPG, rpm must be configured to run GPG
651 and be able to find a key ring with the appropriate keys. By default,
652 rpm uses the same conventions as GPG to find key rings, namely the
653 $GNUPGHOME environment variable. If your key rings are not located
654 where GPG expects them to be, you will need to configure the macro
655 %_gpg_path to be the location of the GPG key rings to use.
656 For compatibility with older versions of GPG, PGP, and rpm, only V3
658 OpenPGP signature packets should be configured. Either DSA or RSA ver‐
659 ification algorithms can be used, but DSA is preferred.
660 If you want to be able to sign packages you create yourself, you also
662 need to create your own public and secret key pair (see the GPG man‐
663 ual). You will also need to configure the rpm macros
664 %_signature
666 The signature type. Right now only gpg and pgp are supported.
667 %_gpg_name
669 The name of the "user" whose key you wish to use to sign your
670 packages.
671 For example, to be able to use GPG to sign packages as the user "John
673 Doe <jdoe@foo.com>" from the key rings located in /etc/rpm/.gpg using
674 the executable /usr/bin/gpg you would include
675 %_signature gpg
677 %_gpg_path /etc/rpm/.gpg
678 %_gpg_name John Doe <jdoe@foo.com>
679 %_gpgbin /usr/bin/gpg
680 in a macro configuration file. Use /etc/rpm/macros for per-system con‐
682 figuration and ~/.rpmmacros for per-user configuration.
683 REBUILD DATABASE OPTIONS
685 The general form of an rpm rebuild database command is
686 rpm {--initdb|--rebuilddb} [-v] [--dbpath DIRECTORY] [--root DIRECTORY]
688 Use --initdb to create a new database if one doesn't already exist
691 (existing database is not overwritten), use --rebuilddb to rebuild the
692 database indices from the installed package headers.
693 SHOWRC
695 The command
696 rpm --showrc
698 shows the values rpm will use for all of the options are currently set
700 in rpmrc and macros configuration file(s).
701 FTP/HTTP OPTIONS
703 rpm can act as an FTP and/or HTTP client so that packages can be
704 queried or installed from the internet. Package files for install,
705 upgrade, and query operations may be specified as an ftp or http style
706 URL:
707 ftp://USER:PASSWORD@HOST:PORT/path/to/package.rpm
709 If the :PASSWORD portion is omitted, the password will be prompted for
711 (once per user/hostname pair). If both the user and password are omit‐
712 ted, anonymous ftp is used. In all cases, passive (PASV) ftp transfers
713 are performed.
714 rpm allows the following options to be used with ftp URLs:
716 --ftpproxy HOST
718 The host HOST will be used as a proxy server for all ftp trans‐
719 fers, which allows users to ftp through firewall machines which
720 use proxy systems. This option may also be specified by config‐
721 uring the macro %_ftpproxy.
722 --ftpport PORT
724 The TCP PORT number to use for the ftp connection on the proxy
725 ftp server instead of the default port. This option may also be
726 specified by configuring the macro %_ftpport.
727 rpm allows the following options to be used with http URLs:
729 --httpproxy HOST
731 The host HOST will be used as a proxy server for all http trans‐
732 fers. This option may also be specified by configuring the macro
733 %_httpproxy.
734 --httpport PORT
736 The TCP PORT number to use for the http connection on the proxy
737 http server instead of the default port. This option may also be
738 specified by configuring the macro %_httpport.
739
741 Executing rpmbuild
742 The build modes of rpm are now resident in the /usr/bin/rpmbuild exe‐
743 cutable. Although legacy compatibility provided by the popt aliases
744 below has been adequate, the compatibility is not perfect; hence build
745 mode compatibility through popt aliases is being removed from rpm.
746 Install the rpmbuild package, and see rpmbuild(8) for documentation of
747 all the rpm build modes previously documented here in rpm(8).
748 Add the following lines to /etc/popt if you wish to continue invoking
750 rpmbuild from the rpm command line:
751 rpm exec --bp rpmb -bp
753 rpm exec --bc rpmb -bc
754 rpm exec --bi rpmb -bi
755 rpm exec --bl rpmb -bl
756 rpm exec --ba rpmb -ba
757 rpm exec --bb rpmb -bb
758 rpm exec --bs rpmb -bs
759 rpm exec --tp rpmb -tp
760 rpm exec --tc rpmb -tc
761 rpm exec --ti rpmb -ti
762 rpm exec --tl rpmb -tl
763 rpm exec --ta rpmb -ta
764 rpm exec --tb rpmb -tb
765 rpm exec --ts rpmb -ts
766 rpm exec --rebuild rpmb --rebuild
767 rpm exec --recompile rpmb --recompile
768 rpm exec --clean rpmb --clean
769 rpm exec --rmsource rpmb --rmsource
770 rpm exec --rmspec rpmb --rmspec
771 rpm exec --target rpmb --target
772 rpm exec --short-circuit rpmb --short-circuit
773
775 rpmrc Configuration
776 /usr/lib/rpm/rpmrc
777 /usr/lib/rpm/redhat/rpmrc
778 /etc/rpmrc
779 ~/.rpmrc
780 Macro Configuration
782 /usr/lib/rpm/macros
783 /usr/lib/rpm/redhat/macros
784 /etc/rpm/macros
785 ~/.rpmmacros
786 Database
788 /var/lib/rpm/Basenames
789 /var/lib/rpm/Conflictname
790 /var/lib/rpm/Dirnames
791 /var/lib/rpm/Filemd5s
792 /var/lib/rpm/Group
793 /var/lib/rpm/Installtid
794 /var/lib/rpm/Name
795 /var/lib/rpm/Packages
796 /var/lib/rpm/Providename
797 /var/lib/rpm/Provideversion
798 /var/lib/rpm/Pubkeys
799 /var/lib/rpm/Removed
800 /var/lib/rpm/Requirename
801 /var/lib/rpm/Requireversion
802 /var/lib/rpm/Sha1header
803 /var/lib/rpm/Sigmd5
804 /var/lib/rpm/Triggername
805 Temporary
807 /var/tmp/rpm*
808
810 popt(3),
811 rpm2cpio(8),
812 rpmbuild(8),
813 rpm --help - as rpm supports customizing the options via popt aliases
815 it's impossible to guarantee that what's described in the manual
816 matches what's available.
817 http://www.rpm.org/ <URL:http://www.rpm.org/>
820
822 Marc Ewing <marc@redhat.com>
823 Jeff Johnson <jbj@redhat.com>
824 Erik Troan <ewt@redhat.com>
825Red Hat, Inc. 09 June 2002 RPM(8)