| 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-RPMRC" "5" "2026-04-10" "RPM 6.0.1" |
| 9 |
.PP |
| 10 |
.SH NAME |
| 11 |
\fBrpm-rpmrc\fR - rpm platform compatibility configuration |
| 12 |
.PP |
| 13 |
.SH SYNOPSIS |
| 14 |
\fIVARIABLE\fR: {\fIARCH\fR|\fIOS\fR}: \fIVALUE\fR .\&.\&.\& |
| 15 |
.PP |
| 16 |
\fIVARIABLE\fR: \fIARCH\fR \fIVALUE\fR |
| 17 |
.PP |
| 18 |
.SH FILES |
| 19 |
\fI/usr/lib/rpm/rpmrc\fR |
| 20 |
.br |
| 21 |
\fI/usr/lib/rpm/<vendor>/rpmrc\fR |
| 22 |
.br |
| 23 |
\fI/etc/rpmrc\fR |
| 24 |
.br |
| 25 |
\fI\(ti/.\&config/rpm/rpmrc\fR |
| 26 |
.PP |
| 27 |
.SH DESCRIPTION |
| 28 |
The low-level machine architecture and OS configuration in \fBrpm\fR is |
| 29 |
managed via a set of rpmrc files as defined by the \fIrpmrc path\fR.\& |
| 30 |
Most users never need to look at, much less touch these files.\& |
| 31 |
.PP |
| 32 |
Each file in the colon separated \fIrpmrc path\fR is read sequentially by |
| 33 |
\fBrpm\fR for configuration information.\& Tildes will be expanded to the |
| 34 |
value of the environment variable \fBHOME\fR.\& |
| 35 |
The first file in the path must exist, others are considered optional.\& |
| 36 |
.PP |
| 37 |
If a value is defined multiple times, the last entry wins.\& The default |
| 38 |
\fIrpmrc path\fR uses this to achieve the following hierarchy of platform |
| 39 |
configuration: |
| 40 |
.PD 0 |
| 41 |
.IP 1. 4 |
| 42 |
Generic \fBrpm\fR factory defaults |
| 43 |
.IP 2. 4 |
| 44 |
Vendor (distribution) specific configuration |
| 45 |
.IP 3. 4 |
| 46 |
Host specific configuration |
| 47 |
.IP 4. 4 |
| 48 |
User specific configuration |
| 49 |
.PD |
| 50 |
.PP |
| 51 |
In older rpm versions the path of per-user rpmrc was \fI\(ti/.\&rpmrc\fR.\& |
| 52 |
This is still processed if it exists and the new configuration directory |
| 53 |
does not exist.\& |
| 54 |
.PP |
| 55 |
.SH CONFIGURATION |
| 56 |
\fIARCH\fR and \fIOS\fR relate to \fBuname\fR(2) machine and operating system |
| 57 |
information, but are not 1:1 equivalent.\& |
| 58 |
The following directives are supported in the rpmrc files: |
| 59 |
.PP |
| 60 |
\fBarch_canon\fR \fIARCH\fR: \fICANON_ARCH\fR \fIARCH_NUM\fR |
| 61 |
.RS 4 |
| 62 |
Names and numbers of known architectures to |
| 63 |
alias different spellings to a canonical one.\& |
| 64 |
\fICANON_ARCH\fR is what the \fIARCH\fR entries in other rpmrc |
| 65 |
directives refer to.\& |
| 66 |
.PP |
| 67 |
The number is not used for any calculations by \fBrpm\fR but |
| 68 |
must be present for historical reasons.\& |
| 69 |
.PP |
| 70 |
.RE |
| 71 |
\fBarch_compat\fR: \fIARCH\fR: \fICOMPAT_ARCH\fR .\&.\&.\& |
| 72 |
.RS 4 |
| 73 |
Declare compatibility between machine architectures, |
| 74 |
ie.\& \fIARCH\fR machines can install packages for \fICOMPAT_ARCH\fR |
| 75 |
architecture.\& |
| 76 |
.PP |
| 77 |
.RE |
| 78 |
\fBarchcolor\fR: \fIARCH\fR \fICOLOR\fR |
| 79 |
.RS 4 |
| 80 |
Declare the "color" of \fIARCH\fR.\& The color relates to the word length |
| 81 |
aka bitness of the architecture: |
| 82 |
.PD 0 |
| 83 |
.IP \(bu 4 |
| 84 |
\fB0\fR means none (noarch packages and similar) |
| 85 |
.IP \(bu 4 |
| 86 |
\fB1\fR means 32-bit |
| 87 |
.IP \(bu 4 |
| 88 |
\fB2\fR means 64-bit |
| 89 |
.PD |
| 90 |
.PP |
| 91 |
.RE |
| 92 |
\fBbuildarch_compat\fR: \fIARCH\fR: \fICOMPAT_ARCH\fR .\&.\&.\& |
| 93 |
.RS 4 |
| 94 |
Declare compatibility between build architectures targets, |
| 95 |
ie.\& \fIARCH\fR machines can produce \fICOMPAT_ARCH\fR binaries.\& |
| 96 |
.PP |
| 97 |
.RE |
| 98 |
\fBbuildarchtranslate\fR: \fIARCH\fR: \fITRANSLATE_ARCH\fR |
| 99 |
.RS 4 |
| 100 |
Automatically translate detected host architecture \fIARCH\fR to |
| 101 |
\fITRANSLATE_ARCH\fR when building packages.\& This is used to map |
| 102 |
sub-architectures to a main one, for example when building on a |
| 103 |
\fBx86_64_v2\fR host we typically want the generated package to be |
| 104 |
of the main \fBx86_64\fR architecture.\& |
| 105 |
.PP |
| 106 |
.RE |
| 107 |
\fBoptflags\fR: \fIARCH\fR \fIOPTFLAGS\fR |
| 108 |
.RS 4 |
| 109 |
Compiler flags to use when building packages for \fIARCH\fR architecture.\& |
| 110 |
The \fIOPTFLAGS\fR value is available as \fB%{optflags}\fR macro in |
| 111 |
spec files.\& |
| 112 |
.PP |
| 113 |
.RE |
| 114 |
\fBos_canon\fR: \fIOS\fR: \fICANON_OS\fR \fIOS_NUM\fR |
| 115 |
.RS 4 |
| 116 |
Names and numbers of known operating systems to |
| 117 |
alias different spellings to a canonical one.\& |
| 118 |
\fICANON_OS\fR is what the \fIOS\fR entries in other rpmrc directives |
| 119 |
refer to.\& |
| 120 |
.PP |
| 121 |
The number is not used for any calculations by \fBrpm\fR but |
| 122 |
must be present for historical reasons.\& |
| 123 |
.PP |
| 124 |
.RE |
| 125 |
\fBos_compat\fR: \fIOS\fR: \fICOMPAT_OS\fR .\&.\&.\& |
| 126 |
.RS 4 |
| 127 |
Declare compatibility between operating systems, ie.\& |
| 128 |
\fIOS\fR machine can install packages for \fICOMPAT_OS\fR operating |
| 129 |
system.\& |
| 130 |
.PP |
| 131 |
.RE |
| 132 |
.SH ENVIRONMENT |
| 133 |
If \fBXDG_CONFIG_HOME\fR environment variable is set, it replaces \fI\(ti/.\&config\fR |
| 134 |
in the \fIrpmrc path\fR.\& |
| 135 |
.PP |
| 136 |
.SH SEE ALSO |
| 137 |
\fBrpm\fR(8), \fBrpm-common\fR(8), \fBrpm-config\fR(5), \fBrpm-macros\fR(7) |