folkslinux
/
rpm
mirror of https://github.com/rpm-software-management/rpm.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add quotes in doxygen blocks.

This commit is contained in:
Ralf Corsépius 2007-10-06 04:45:37 +02:00
parent 4770cb41c2
commit acedc1b611
4 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/manual/dependencies
View File

@ -300,9 +300,9 @@ The second, --requires, shows the other packages that a package requires
to be installed, along with any version number checking.
There are also two new ways to search for packages. Running a query with
--whatrequires <item> queries all of the packages that require <item>.
Similarly, running --whatprovides <item> queries all of the packages that
provide the <item> virtual package. Note that querying for package that
--whatrequires \<item\> queries all of the packages that require \<item\>.
Similarly, running --whatprovides \<item\> queries all of the packages that
provide the \<item\> virtual package. Note that querying for package that
provides "python" will not return anything, as python is a package, not
a virtual package.

8
doc/manual/macros
View File

@ -6,7 +6,7 @@ argc/argv processing on white space separated tokens to the next newline.
During macro expansion, both flags and arguments are available as macros
which are deleted at the end of macro expansion. Macros can be used
(almost) anywhere in a spec file, and, in particular, in "included file
lists" (i.e. those read in using %files -f <file>). In addition, macros
lists" (i.e. those read in using %files -f \<file\>). In addition, macros
can be nested, hiding the previous definition for the duration of the
expansion of the macro which contains nested macros.
@ -18,7 +18,7 @@ To define a macro use:
%define <name>[(opts)] <body>
\endverbatim
All whitespace surrounding <body> is removed. Name may be composed
All whitespace surrounding \<body\> is removed. Name may be composed
of alphanumeric characters, and the character `_' and must be at least
3 characters in length. A macro without an (opts) field is "simple" in that
only recursive macro expansion is performed. A parameterized macro contains
@ -145,9 +145,9 @@ or
\endverbatim
The %{...} form allows you to place the expansion adjacent to other text.
The %<name> form, if a parameterized macro, will do argc/argv processing
The %\<name\> form, if a parameterized macro, will do argc/argv processing
of the rest of the line as described above. Normally you will likely want
to invoke a parameterized macro by using the %<name> form so that
to invoke a parameterized macro by using the %\<name\> form so that
parameters are expanded properly.
Example:

2
doc/manual/spec
View File

@ -9,7 +9,7 @@ include whitespace and may include a hyphen '-' (unlike version and release
tags). Names should not include any numeric operators ('<', '>','=') as
future versions of rpm may need to reserve characters other than '-'.
By default subpackages are named by prepending `<main package>-' to
By default subpackages are named by prepending `\<main package\>-' to
the subpackages name(s). If you wish to change the name of a
subpackage (most commonly this is to change the '-' to '.'), then you
must specify the full name with the -n argument in the %package

2
doc/manual/triggers
View File

@ -109,7 +109,7 @@ Trigger specifications are of the form:
\endverbatim
The -n and -p arguments are the same as for %post scripts. The
<trigger> portion is syntactically equivalent to a "Requires"
\<trigger\> portion is syntactically equivalent to a "Requires"
specification (version numbers may be used). If multiple items are
given (comma separated), the trigger is run when *any* of those
conditions becomes true (the , can be read as "or"). For example: