Move "dot-error-breaks-index" example to new do-and-don't section devoted
to .error. Translators note: this is a block copy, there is no text changed. This and the previous commit inspired by: David Thiel <lx at redundancy dot redundancy dot org>
This commit is contained in:
parent
ae83502fe3
commit
507323ffc7
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=26058
1 changed files with 17 additions and 16 deletions
|
@ -6211,22 +6211,6 @@ as .putsy.conf and edit it.</programlisting>
|
|||
(See <xref linkend="dads-dot-error">.)</para>
|
||||
</note>
|
||||
|
||||
<example id="dot-error-breaks-index">
|
||||
<title>How to avoid using <literal>.error</literal></title>
|
||||
<para>Assume that someone has the line
|
||||
<programlisting>USE_POINTYHAT=yes</programlisting>
|
||||
in <filename>make.conf</filename>. The first of
|
||||
the next two <filename>Makefile</filename> snippets will
|
||||
cause <command>make index</command> to fail, while the
|
||||
second one will not:</para>
|
||||
<programlisting>.if USE_POINTYHAT
|
||||
.error "POINTYHAT is not supported"
|
||||
.endif</programlisting>
|
||||
<programlisting>.if USE_POINTYHAT
|
||||
IGNORE=POINTYHAT is not supported
|
||||
.endif</programlisting>
|
||||
</example>
|
||||
|
||||
<para>If <command>make describe</command> produces a string
|
||||
rather than an error message, you are probably safe. See
|
||||
<filename>bsd.port.mk</filename> for the meaning of the
|
||||
|
@ -9397,6 +9381,23 @@ bacula:*:910:</programlisting>
|
|||
(see <xref linkend="make-describe">). However, even more
|
||||
trivial commands such as <command>make -V maintainer</command>
|
||||
also fail in this scenario. This is not acceptable.</para>
|
||||
|
||||
<example id="dot-error-breaks-index">
|
||||
<title>How to avoid using <literal>.error</literal></title>
|
||||
<para>Assume that someone has the line
|
||||
<programlisting>USE_POINTYHAT=yes</programlisting>
|
||||
in <filename>make.conf</filename>. The first of
|
||||
the next two <filename>Makefile</filename> snippets will
|
||||
cause <command>make index</command> to fail, while the
|
||||
second one will not:</para>
|
||||
<programlisting>.if USE_POINTYHAT
|
||||
.error "POINTYHAT is not supported"
|
||||
.endif</programlisting>
|
||||
<programlisting>.if USE_POINTYHAT
|
||||
IGNORE=POINTYHAT is not supported
|
||||
.endif</programlisting>
|
||||
</example>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="dads-workarounds">
|
||||
|
|
Loading…
Reference in a new issue