Whitespace, translators can ignore.

Sponsored by:	Absolight, The FreeBSD Foundation
This commit is contained in:
Mathieu Arnold 2017-08-02 12:19:45 +00:00
parent 6fa1478dc3
commit f20e82aec4
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=50620
2 changed files with 23 additions and 14 deletions

View file

@ -279,7 +279,8 @@
</listitem> </listitem>
<listitem> <listitem>
<para><link linkend="dads-noinstall">BROKEN_<replaceable>*</replaceable></link></para> <para><link
linkend="dads-noinstall">BROKEN_<replaceable>*</replaceable></link></para>
</listitem> </listitem>
<listitem> <listitem>
@ -287,23 +288,28 @@
</listitem> </listitem>
<listitem> <listitem>
<para><link linkend="dads-noinstall">IGNORE_<replaceable>*</replaceable></link></para> <para><link
linkend="dads-noinstall">IGNORE_<replaceable>*</replaceable></link></para>
</listitem> </listitem>
<listitem> <listitem>
<para><link linkend="dads-noinstall">ONLY_FOR_ARCHS</link></para> <para><link
linkend="dads-noinstall">ONLY_FOR_ARCHS</link></para>
</listitem> </listitem>
<listitem> <listitem>
<para><link linkend="dads-noinstall">ONLY_FOR_ARCHS_REASON<replaceable>*</replaceable></link></para> <para><link
linkend="dads-noinstall">ONLY_FOR_ARCHS_REASON<replaceable>*</replaceable></link></para>
</listitem> </listitem>
<listitem> <listitem>
<para><link linkend="dads-noinstall">NOT_FOR_ARCHS</link></para> <para><link
linkend="dads-noinstall">NOT_FOR_ARCHS</link></para>
</listitem> </listitem>
<listitem> <listitem>
<para><link linkend="dads-noinstall">NOT_FOR_ARCHS_REASON<replaceable>*</replaceable></link></para> <para><link
linkend="dads-noinstall">NOT_FOR_ARCHS_REASON<replaceable>*</replaceable></link></para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
@ -390,11 +396,14 @@
<filename>bsd.port.mk</filename> that do not belong in any <filename>bsd.port.mk</filename> that do not belong in any
of the previous section blocks.</para> of the previous section blocks.</para>
<para>Order is not important, however try to keep similar variables together. <para>Order is not important, however try to keep similar
For example uid and gid variables <varname>USERS</varname> and <varname>GROUPS</varname>. variables together. For example uid and gid variables
Configuration variables <varname>CONFIGURE_<replaceable>*</replaceable></varname> and <varname>USERS</varname> and <varname>GROUPS</varname>.
<varname><replaceable>*</replaceable>_CONFIGURE</varname>. List of files, and directories Configuration variables
<varname>PORTDOCS</varname> and <varname>PORTEXAMPLES</varname>.</para> <varname>CONFIGURE_<replaceable>*</replaceable></varname> and
<varname><replaceable>*</replaceable>_CONFIGURE</varname>. List
of files, and directories <varname>PORTDOCS</varname> and
<varname>PORTEXAMPLES</varname>.</para>
</sect1> </sect1>
<sect1 xml:id="porting-order-options"> <sect1 xml:id="porting-order-options">

View file

@ -16,9 +16,9 @@
comments (ones between brackets).</para> comments (ones between brackets).</para>
<para>The format shown is the recommended one for ordering <para>The format shown is the recommended one for ordering
variables, empty lines between sections, and so on. This format is variables, empty lines between sections, and so on. This format
designed so that the most important information is easy to locate. is designed so that the most important information is easy to
We recommend using locate. We recommend using
<link linkend="porting-portlint">portlint</link> to check the <link linkend="porting-portlint">portlint</link> to check the
<filename>Makefile</filename>.</para> <filename>Makefile</filename>.</para>