OpenPKG CVS Repository http://cvs.openpkg.org/ ____________________________________________________________________________
Server: cvs.openpkg.org Name: Christoph Schug Root: /v/openpkg/cvs Email: [EMAIL PROTECTED] Module: openpkg-src Date: 30-Jan-2007 18:36:30 Branch: HEAD Handle: 2007013017362900 Modified files: openpkg-src/openpkg HISTORY rpmtool.8 rpmtool.pod Log: typos in rpmtool man page Summary: Revision Changes Path 1.421 +1 -1 openpkg-src/openpkg/HISTORY 1.12 +4 -4 openpkg-src/openpkg/rpmtool.8 1.17 +4 -4 openpkg-src/openpkg/rpmtool.pod ____________________________________________________________________________ patch -p0 <<'@@ .' Index: openpkg-src/openpkg/HISTORY ============================================================================ $ cvs diff -u -r1.420 -r1.421 HISTORY --- openpkg-src/openpkg/HISTORY 30 Jan 2007 13:15:41 -0000 1.420 +++ openpkg-src/openpkg/HISTORY 30 Jan 2007 17:36:29 -0000 1.421 @@ -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 **** @@ . patch -p0 <<'@@ .' Index: openpkg-src/openpkg/rpmtool.8 ============================================================================ $ cvs diff -u -r1.11 -r1.12 rpmtool.8 --- openpkg-src/openpkg/rpmtool.8 25 Aug 2006 08:58:49 -0000 1.11 +++ openpkg-src/openpkg/rpmtool.8 30 Jan 2007 17:36:29 -0000 1.12 @@ -182,7 +182,7 @@ 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 @@ .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 @@ .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 @@ 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 @@ . patch -p0 <<'@@ .' Index: openpkg-src/openpkg/rpmtool.pod ============================================================================ $ cvs diff -u -r1.16 -r1.17 rpmtool.pod --- openpkg-src/openpkg/rpmtool.pod 1 Jan 2007 17:40:20 -0000 1.16 +++ openpkg-src/openpkg/rpmtool.pod 30 Jan 2007 17:36:29 -0000 1.17 @@ -79,7 +79,7 @@ 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 @@ 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 @@ 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 @@ 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. @@ . ______________________________________________________________________ OpenPKG http://openpkg.org CVS Repository Commit List openpkg-cvs@openpkg.org