Browse Source

typos in rpmtool man page

master
Christoph Schug 19 years ago committed by Ralf S. Engelschall
parent
commit
a6530e0701
  1. 2
      openpkg/HISTORY
  2. 8
      openpkg/rpmtool.8
  3. 8
      openpkg/rpmtool.pod

2
openpkg/HISTORY

@ -2,7 +2,7 @@
2007
====
20070130 minor fixes in rpmtool
20070130 minor fixes in rpmtool and the corresponding man page
20070130 upgrade to cURL 7.16.1
20070105 **** RELEASE AS PART OF OPENPKG 2.20070105 ****

8
openpkg/rpmtool.8

@ -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

8
openpkg/rpmtool.pod

@ -79,7 +79,7 @@ it outputs "-O2 -pipe" for GNU C/C++ compiler).
Example:
CC="$CC" CFLAGS=`rpmtool mflags -O $CC` ./configure ...
CC="$CC" CFLAGS=`rpmtool cflags -O $CC` ./configure ...
=item B<cppflags> [B<-p> I<prefix>] [[C<+|->I<subdir> ...]
@ -124,7 +124,7 @@ provided:
RPM requires that all tags (like C<%attr(...)> or C<%dir>) 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 rpmtool(1)
file lists, because all paths cannot be left-aligned. With rpmtool(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 RPM.
@ -133,7 +133,7 @@ positions for RPM.
RPM supports simple wildcard patterns like C</path/*> or C</path/[a-z]>,
etc. Sometimes it is convenient, to also have (in addition to character
sets) string sets like C</path/{foo,bar,quux}>. rpmtool(1) provides this
sets) string sets like C</path/{foo,bar,quux}>. rpmtool(8) provides this
by syntactically (without checking the filesystem) expanding those
string sets.
@ -144,7 +144,7 @@ B<files> command was implemented. Although RPM allows one to specify a
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
C<%attr(...)> tag is required). rpmtool(1) now supports overriding
C<%attr(...)> tag is required). rpmtool(8) now supports overriding
entries, i.e., if a path occurs multiple times, only the last occurance
is kept.

Loading…
Cancel
Save