os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Whitespace fixes. Translators please ignore.

Browse source
This commit is contained in:
Mark Linimon 2004-12-14 18:38:46 +00:00
parent 4d39466453
commit 86f3046b11
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=23216
1 changed files with 23 additions and 23 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
en_US.ISO8859-1/books/porters-handbook/book.sgml
View file

@ -7330,7 +7330,7 @@ Reference: <http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00
</row>
<row>
<entry>5.2-CURRENT after marking Bluetooth code as
non-i386 specific.
non-i386 specific.
</entry>
<entry>502121</entry>
</row>
@ -7443,7 +7443,7 @@ Reference: &lt;http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00
</row>
<row>
<entry>6.0-CURRENT after addition of 802.11 framework
updates.
updates.
</entry>
<entry>600007</entry>
</row>
@ -8000,20 +8000,20 @@ bopm:*:717:</programlisting>
<title>Marking a port <makevar>BROKEN</makevar>, <makevar>FORBIDDEN</makevar>, or otherwise not installable</title>
<para>In certain cases users should be prevented from installing
a port. For instance, there may come a time when a particular port
will contain a security vulnerability, will be radically
broken and needs many hours of tender loving care, or is
generally obsoleted, but for one reason or another should
remain in the tree (and get fixed, right?). To tell a user that
a port should not be installed, there are several <command>make</command>
variables that can be used in a port's
<filename>Makefile</filename>. The value of the following
<command>make</command> variables will be the reason that is
given back to users for why the port refuses to install itself.
Please use the correct <command>make</command> variable as
each make variable conveys radically different meanings to
both users, and to automated systems that depend on the
<filename>Makefile</filename>s, such as
a port. For instance, there may come a time when a particular port
will contain a security vulnerability, will be radically
broken and needs many hours of tender loving care, or is
generally obsoleted, but for one reason or another should
remain in the tree (and get fixed, right?). To tell a user that
a port should not be installed, there are several
<command>make</command> variables that can be used in a port's
<filename>Makefile</filename>. The value of the following
<command>make</command> variables will be the reason that is
given back to users for why the port refuses to install itself.
Please use the correct <command>make</command> variable as
each make variable conveys radically different meanings to
both users, and to automated systems that depend on the
<filename>Makefile</filename>s, such as
<link linkend="build-cluster">the ports build cluster</link>,
<link linkend="freshports">FreshPorts</link>, and
<link linkend="portsmon">portsmon</link>.</para>
@ -8082,10 +8082,10 @@ bopm:*:717:</programlisting>
<note>
<para>If a port would conflict with a currently installed
port, <link linkend="conflicts">use
<makevar>CONFLICTS</makevar> instead</link>.
<makevar>CONFLICTS</makevar> will set
<makevar>IGNORE</makevar> by itself.</para>
port, <link linkend="conflicts">use
<makevar>CONFLICTS</makevar> instead</link>.
<makevar>CONFLICTS</makevar> will set
<makevar>IGNORE</makevar> by itself.</para>
</note>
<para>If a port sould be marked <makevar>IGNORE</makevar>