Use direct reference to pkg-descr for devel/portlint instead of
mentioning it with <command> macro. Remove trainling spaces.
This commit is contained in:
parent
7474f21269
commit
651f4b2880
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=25722
1 changed files with 11 additions and 11 deletions
|
@ -344,11 +344,11 @@ PLIST_DIRS= lib/X11/oneko</programlisting>
|
||||||
<title>Checking your port with <command>portlint</command></title>
|
<title>Checking your port with <command>portlint</command></title>
|
||||||
|
|
||||||
<para>Please use <command>portlint</command> to see if your port
|
<para>Please use <command>portlint</command> to see if your port
|
||||||
conforms to our guidelines. The <command>portlint</command> program
|
conforms to our guidelines. The <filename role="package">
|
||||||
is part of the ports collection. In particular, you may want to
|
devel/portlint</filename> program is part of the ports collection.
|
||||||
check if the <link linkend="porting-samplem">Makefile</link> is in
|
In particular, you may want to check if the
|
||||||
the right shape and the <link
|
<link linkend="porting-samplem">Makefile</link> is in the right
|
||||||
linkend="porting-pkgname">package</link> is named
|
shape and the <link linkend="porting-pkgname">package</link> is named
|
||||||
appropriately.</para>
|
appropriately.</para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
|
@ -2133,7 +2133,7 @@ PORTEPOCH= 1</programlisting>
|
||||||
<entry><makevar>PORTVERSION</makevar></entry>
|
<entry><makevar>PORTVERSION</makevar></entry>
|
||||||
</row>
|
</row>
|
||||||
</thead>
|
</thead>
|
||||||
|
|
||||||
<tbody>
|
<tbody>
|
||||||
<row>
|
<row>
|
||||||
<entry>0.7.1d</entry>
|
<entry>0.7.1d</entry>
|
||||||
|
@ -5424,8 +5424,8 @@ _DOCSDIR= .
|
||||||
|
|
||||||
<entry>Use Python distutils for configuring, compiling and
|
<entry>Use Python distutils for configuring, compiling and
|
||||||
installing. This is required when the port comes with
|
installing. This is required when the port comes with
|
||||||
<filename>setup.py</filename>. This overrides the
|
<filename>setup.py</filename>. This overrides the
|
||||||
<maketarget>do-build</maketarget> and
|
<maketarget>do-build</maketarget> and
|
||||||
<maketarget>do-install</maketarget> targets
|
<maketarget>do-install</maketarget> targets
|
||||||
and may also override <maketarget>do-configure</maketarget> if
|
and may also override <maketarget>do-configure</maketarget> if
|
||||||
<makevar>GNU_CONFIGURE</makevar> is not defined.</entry>
|
<makevar>GNU_CONFIGURE</makevar> is not defined.</entry>
|
||||||
|
@ -5447,10 +5447,10 @@ _DOCSDIR= .
|
||||||
The <makevar>PYTHON_SITELIBDIR</makevar> variable can be very
|
The <makevar>PYTHON_SITELIBDIR</makevar> variable can be very
|
||||||
useful when installing Python modules.</entry>
|
useful when installing Python modules.</entry>
|
||||||
</row>
|
</row>
|
||||||
|
|
||||||
<row>
|
<row>
|
||||||
<entry><makevar>PYTHONPREFIX_SITELIBDIR</makevar></entry>
|
<entry><makevar>PYTHONPREFIX_SITELIBDIR</makevar></entry>
|
||||||
|
|
||||||
<entry>The PREFIX-clean variant of PYTHON_SITELIBDIR.
|
<entry>The PREFIX-clean variant of PYTHON_SITELIBDIR.
|
||||||
Always use
|
Always use
|
||||||
<literal>%%PYTHON_SITELIBDIR%%</literal> in
|
<literal>%%PYTHON_SITELIBDIR%%</literal> in
|
||||||
|
@ -5461,7 +5461,7 @@ _DOCSDIR= .
|
||||||
|
|
||||||
<row>
|
<row>
|
||||||
<entry><makevar>PYTHON_CMD</makevar></entry>
|
<entry><makevar>PYTHON_CMD</makevar></entry>
|
||||||
|
|
||||||
<entry>Python interpreter command line, including version
|
<entry>Python interpreter command line, including version
|
||||||
number.</entry>
|
number.</entry>
|
||||||
</row>
|
</row>
|
||||||
|
|
Loading…
Reference in a new issue