Fix references to NOPORTDOCS, NOPORTDATA and NOPORTEXAMPLES to the

new options framework DOCS, DATA, EXAMPLES options.

Noticed by:	Alexey V. Panfilov <ports@subnets.ru>
Approved by:	bapt, gjb
This commit is contained in:
Guido Falsi 2012-12-08 22:47:14 +00:00
parent a1a6ff8430
commit 3530fbdbfb
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=40308

View file

@ -4922,11 +4922,11 @@ PORTVERSION= 1.0</programlisting>
<makevar>PKGNAME</makevar>.</para>
<para>Make the installation dependent on the variable
<makevar>NOPORTDOCS</makevar> so that users can disable it
<literal>DOCS</literal> option so that users can disable it
in <filename>/etc/make.conf</filename>, like this:</para>
<programlisting>post-install:
.if !defined(NOPORTDOCS)
.if ${PORT_OPTIONS:MDOCS}
${MKDIR} ${DOCSDIR}
${INSTALL_MAN} ${WRKSRC}/docs/xvdocs.ps ${DOCSDIR}
.endif</programlisting>
@ -4968,13 +4968,13 @@ PORTVERSION= 1.0</programlisting>
</itemizedlist>
<note>
<para><makevar>NOPORTDOCS</makevar> only controls additional
<para>The <literal>DOCS</literal> option only controls additional
documentation installed in <makevar>DOCSDIR</makevar>. It
does not apply to standard man pages and info pages.
Things installed in <makevar>DATADIR</makevar> and
<makevar>EXAMPLESDIR</makevar> are controlled by
<makevar>NOPORTDATA</makevar> and
<makevar>NOPORTEXAMPLES</makevar>, respectively.</para>
<literal>DATA</literal> and
<literal>EXAMPLES</literal> options, respectively.</para>
</note>
<para>These variables are exported to
@ -5008,10 +5008,10 @@ PORTVERSION= 1.0</programlisting>
is listed in <makevar>PORTDOCS</makevar> or matched by a
glob pattern from this variable, the entire subtree of
contained files and directories will be registered in the
final packing list. If <makevar>NOPORTDOCS</makevar> is
defined then files and directories listed in
<makevar>PORTDOCS</makevar> would not be installed and
neither would be added to port packing list. Installing the
final packing list. If the <literal>DOCS</literal> option has
been unset then files and directories listed in
<makevar>PORTDOCS</makevar> would not be installed
or added to port packing list. Installing the
documentation at <makevar>PORTDOCS</makevar> as shown above
remains up to the port itself. A typical example of
utilizing <makevar>PORTDOCS</makevar> looks as