Whitespace-only fixes, translators please ignore.

This commit is contained in:
Warren Block 2012-05-29 19:24:26 +00:00
parent cfd1d0962c
commit 6116a7009b
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=38932

View file

@ -4089,14 +4089,13 @@ ${MANPREFIX}/man/de/man3/baz.3.gz</programlisting>
<title>Makefile Options</title>
<para>Many applications can be built with optional or differing
configurations. Examples include
choice of natural (human) language, GUI versus command-line,
or type of database to support. Users may need a different
configuration than the default, so the ports system provides
hooks the port author can use to control which variation
will be built. Supporting these options properly will
make users happy, and effectively provide two or more ports for
the price of one.</para>
configurations. Examples include choice of natural (human)
language, GUI versus command-line, or type of database to
support. Users may need a different configuration than the
default, so the ports system provides hooks the port author
can use to control which variation will be built. Supporting
these options properly will make users happy, and effectively
provide two or more ports for the price of one.</para>
<sect2>
<title>Knobs</title>
@ -4107,8 +4106,8 @@ ${MANPREFIX}/man/de/man3/baz.3.gz</programlisting>
<makevar>WITHOUT_<replaceable>*</replaceable></makevar></title>
<para>These variables are designed to be set by the system
administrator. There are many that are standardized in the
<ulink
administrator. There are many that are standardized in
the <ulink
url="http://www.freebsd.org/cgi/cvsweb.cgi/ports/KNOBS?rev=HEAD&amp;content-type=text/x-cvsweb-markup"><filename>ports/KNOBS</filename></ulink>
file.</para>
@ -4205,9 +4204,9 @@ ${MANPREFIX}/man/de/man3/baz.3.gz</programlisting>
<sect3>
<title>Background</title>
<para>The <makevar>OPTIONS_*</makevar> variables give the user
installing the port a dialog showing the available options,
and then saves those options to
<para>The <makevar>OPTIONS_*</makevar> variables give the
user installing the port a dialog showing the available
options, and then saves those options to
<filename>/var/db/ports/<makevar>${UNIQUENAME}</makevar>/options</filename>.
The next time the port is built, the options are
reused.</para>
@ -4217,10 +4216,10 @@ ${MANPREFIX}/man/de/man3/baz.3.gz</programlisting>
the framework checks for
<filename>/var/db/ports/<makevar>${UNIQUENAME}</makevar>/options</filename>.
If that file does not exist, the values of
<makevar>OPTIONS_*</makevar> are used, and a dialog box is displayed where
the options can be enabled or disabled. Then the
<filename>options</filename> file is saved and the
configured variables are used when building the
<makevar>OPTIONS_*</makevar> are used, and a dialog box is
displayed where the options can be enabled or disabled.
Then the <filename>options</filename> file is saved and
the configured variables are used when building the
port.</para>
<para>If a new version of the port adds new
@ -4237,8 +4236,8 @@ ${MANPREFIX}/man/de/man3/baz.3.gz</programlisting>
<title>Syntax</title>
<para><makevar>OPTIONS_DEFINE</makevar> contains a list of
<makevar>OPTIONS</makevar> to be used. These are independent
of each other and are not grouped:</para>
<makevar>OPTIONS</makevar> to be used. These are
independent of each other and are not grouped:</para>
<programlisting>OPTIONS_DEFINE= OPT1 OPT2</programlisting>
@ -4262,12 +4261,11 @@ OPT6_DESC= Describe OPT6</programlisting>
<tip>
<para>When describing options, view it from the
perspective of the user: <quote>What does it do?</quote>
and <quote>Why would I want to enable this?</quote> Do
and <quote>Why would I want to enable this?</quote> Do
not just repeat the name. For example, describing the
<literal>NLS</literal> option as
<quote>include NLS support</quote> does not help the
user who can already see the option name but may not
know what it means. Describing it as <quote>Native
Language Support via gettext utilities</quote> is
much more helpful.</para>
@ -5555,10 +5553,10 @@ PLIST_SUB+= NLS="@comment "
<title>Using <application>Perl</application></title>
<para>If <makevar>MASTER_SITES</makevar> is set to
<makevar>MASTER_SITE_PERL_CPAN</makevar>, then the preferred value
of <makevar>MASTER_SITE_SUBDIR</makevar> is the top-level
hierarchy name. For example, the recommended value for
<literal>p5-Module-Name</literal> is
<makevar>MASTER_SITE_PERL_CPAN</makevar>, then the preferred
value of <makevar>MASTER_SITE_SUBDIR</makevar> is the
top-level hierarchy name. For example, the recommended value
for <literal>p5-Module-Name</literal> is
<literal>Module</literal>. The top-level hierarchy can be
examined at <ulink
url="http://cpan.org/modules/by-module/">cpan.org</ulink>.
@ -6976,13 +6974,15 @@ QT_COMPONENTS= moc_build qmake_build rcc_build uic_build</programlisting>
<row>
<entry><makevar>APACHEMODDIR</makevar></entry>
<entry>Directory for Apache modules. This variable is
automatically expanded in <filename>pkg-plist</filename>.</entry>
automatically expanded in
<filename>pkg-plist</filename>.</entry>
</row>
<row>
<entry><makevar>APACHEINCLUDEDIR</makevar></entry>
<entry>Directory for Apache headers. This variable is
automatically expanded in <filename>pkg-plist</filename>.</entry>
automatically expanded in
<filename>pkg-plist</filename>.</entry>
</row>
<row>