| 1 |
.\" Generated by scdoc 1.11.4 |
| 2 |
.\" Complete documentation for this program is not available as a GNU info page |
| 3 |
.ie \n(.g .ds Aq \(aq |
| 4 |
.el .ds Aq ' |
| 5 |
.nh |
| 6 |
.ad l |
| 7 |
.\" Begin generated content: |
| 8 |
.TH "RPM-MANIFEST" "5" "2026-04-10" "RPM 6.0.1" |
| 9 |
.PP |
| 10 |
.SH NAME |
| 11 |
\fBrpm-manifest\fR - rpm package manifest file format |
| 12 |
.PP |
| 13 |
.SH SYNOPSIS |
| 14 |
\fIGLOB\fR .\&.\&.\& |
| 15 |
.PP |
| 16 |
# \fICOMMENT\fR |
| 17 |
.PP |
| 18 |
.SH DESCRIPTION |
| 19 |
RPM package manifest files are plaintext files containing one or |
| 20 |
more \fBglob\fR(7) entries that are expected to match either RPM package files |
| 21 |
or other package manifests.\& |
| 22 |
.PP |
| 23 |
Package manifests can be used as a way to document installation of large |
| 24 |
package sets in an RPM-native way, without having to set up repositories |
| 25 |
and configure external dependency resolver programs to use them.\& |
| 26 |
For end-user purposes manifests are clumsy, but for example to quickly |
| 27 |
install a base image from a pre-determined set of package versions from |
| 28 |
local directory, a manifest may well be easier and faster than using |
| 29 |
a depsolver for the task.\& A manifest can be also used to work around |
| 30 |
command line length limitations.\& |
| 31 |
.PP |
| 32 |
Relative globs are interpreted relative to the user'\&s current directory.\& |
| 33 |
Multiple globs per line are permitted, but for readability it'\&s |
| 34 |
recommended to use one per line instead.\& |
| 35 |
.PP |
| 36 |
Lines beginning with \fB#\fR are considered comments.\& Empty lines and |
| 37 |
lines consisting of only whitespace are ignored.\& |
| 38 |
.PP |
| 39 |
.SH EXAMPLES |
| 40 |
.PP |
| 41 |
.SS Example 1. Manifest of all myproj-1.0 releases and their dependencies |
| 42 |
.nf |
| 43 |
.RS 4 |
| 44 |
/mnt/myproj/rpm/myproj-1\&.0-*\&.x86_64\&.rpm |
| 45 |
/mnt/deplib/rpm/mylib-2\&.1-*\&.x86_64\&.rpm |
| 46 |
.fi |
| 47 |
.RE |
| 48 |
.PP |
| 49 |
.SS Example 2. Manifest of all noarch packages in the default rpmbuild(1) location |
| 50 |
.nf |
| 51 |
.RS 4 |
| 52 |
~/rpmbuild/RPMS/noarch/*\&.rpm |
| 53 |
.fi |
| 54 |
.RE |
| 55 |
.PP |
| 56 |
.SS Example 3. Manifest as a simple base image |
| 57 |
.PP |
| 58 |
Create a manifest called \fBmymanifest.\&mft\fR of currently installed packages, |
| 59 |
assuming a base path of \fB/mnt/Packages\fR for the RPM package files, and install |
| 60 |
it to an alternative system root at \fB/srv/test\fR: |
| 61 |
.PP |
| 62 |
.nf |
| 63 |
.RS 4 |
| 64 |
rpm -qa --qf \&'/mnt/Packages/%{nevra}\&.rpm\\n\&' > mymanifest\&.mft |
| 65 |
rpm -Uv --root /srv/test mymanifest\&.mft |
| 66 |
.fi |
| 67 |
.RE |
| 68 |
.PP |
| 69 |
.SH SEE ALSO |
| 70 |
\fBrpm\fR(8) \fBrpm-common\fR(8) |