|
|
|
|
@ -182,7 +182,7 @@ it outputs \*(L"\-O2 \-pipe\*(R" for \s-1GNU\s0 C/\*(C+ compiler).
|
|
|
|
|
Example: |
|
|
|
|
.Sp |
|
|
|
|
.Vb 1 |
|
|
|
|
\& CC="$CC" CFLAGS=`rpmtool mflags -O $CC` ./configure ... |
|
|
|
|
\& CC="$CC" CFLAGS=`rpmtool cflags -O $CC` ./configure ... |
|
|
|
|
.Ve |
|
|
|
|
.ie n .IP "\fBcppflags\fR [\fB\-p\fR \fIprefix\fR] [[\*(C`+|\-\*(C'\fR\fIsubdir ...]" 4 |
|
|
|
|
.el .IP "\fBcppflags\fR [\fB\-p\fR \fIprefix\fR] [[\f(CW\*(C`+|\-\*(C'\fR\fIsubdir\fR ...]" 4 |
|
|
|
|
@ -229,7 +229,7 @@ provided:
|
|
|
|
|
.IX Item "Trailing Tags" |
|
|
|
|
\&\s-1RPM\s0 requires that all tags (like \f(CW\*(C`%attr(...)\*(C'\fR or \f(CW%dir\fR) preceed the |
|
|
|
|
path in a file list entry. This sometimes leads to ugly and unreadable |
|
|
|
|
file lists, because all paths cannot be left\-aligned. With \fIrpmtool\fR\|(1) |
|
|
|
|
file lists, because all paths cannot be left\-aligned. With \fIrpmtool\fR\|(8) |
|
|
|
|
tags in the input file list can be at leading and trailing positions. |
|
|
|
|
The output file list will nevertheless have all tags in leading |
|
|
|
|
positions for \s-1RPM\s0. |
|
|
|
|
@ -237,7 +237,7 @@ positions for \s-1RPM\s0.
|
|
|
|
|
.IX Item "Syntactical Set Pattern" |
|
|
|
|
\&\s-1RPM\s0 supports simple wildcard patterns like \f(CW\*(C`/path/*\*(C'\fR or \f(CW\*(C`/path/[a\-z]\*(C'\fR, |
|
|
|
|
etc. Sometimes it is convenient, to also have (in addition to character |
|
|
|
|
sets) string sets like \f(CW\*(C`/path/{foo,bar,quux}\*(C'\fR. \fIrpmtool\fR\|(1) provides this |
|
|
|
|
sets) string sets like \f(CW\*(C`/path/{foo,bar,quux}\*(C'\fR. \fIrpmtool\fR\|(8) provides this |
|
|
|
|
by syntactically (without checking the filesystem) expanding those |
|
|
|
|
string sets. |
|
|
|
|
.IP "\fBOverriding Entries\fR" 4 |
|
|
|
|
@ -247,7 +247,7 @@ This is the most important feature and the reason why \fIshtool\fR\|(1)'s
|
|
|
|
|
directory in a file list and then implicitly expands this recursively |
|
|
|
|
into its contents, it unfortunately does not allow one to later |
|
|
|
|
explcitly override particular entries (usually if an individual |
|
|
|
|
\&\f(CW\*(C`%attr(...)\*(C'\fR tag is required). \fIrpmtool\fR\|(1) now supports overriding |
|
|
|
|
\&\f(CW\*(C`%attr(...)\*(C'\fR tag is required). \fIrpmtool\fR\|(8) now supports overriding |
|
|
|
|
entries, i.e., if a path occurs multiple times, only the last occurance |
|
|
|
|
is kept. |
|
|
|
|
.IP "\fBNegation Tag\fR" 4 |
|
|
|
|
|