Remove LATEST_LINK mentions, nobody should use it, ever.
Sponsored by: Absolight
This commit is contained in:
parent
897fac7474
commit
fcc09ead19
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=43748
3 changed files with 18 additions and 58 deletions
|
@ -4014,22 +4014,26 @@ MFC after: 1 month</programlisting>
|
||||||
|
|
||||||
<step>
|
<step>
|
||||||
<para>Upgrade the copied port to the new version.
|
<para>Upgrade the copied port to the new version.
|
||||||
Remember to change the
|
Remember to add or change the
|
||||||
<varname>LATEST_LINK</varname> so there are no
|
<varname>PKGNAMEPREFIX</varname> or
|
||||||
|
<varname>PKGNAMESUFFIX</varname> so there are no
|
||||||
duplicate ports with the same name. In some
|
duplicate ports with the same name. In some
|
||||||
rare cases it may be necessary to change the
|
rare cases it may be necessary to change the
|
||||||
<varname>PORTNAME</varname> instead of
|
<varname>PORTNAME</varname> instead of adding
|
||||||
<varname>LATEST_LINK</varname>, but this should
|
<varname>PKGNAMEPREFIX</varname> or
|
||||||
only be done when it is really needed —
|
<varname>PKGNAMESUFFIX</varname>, but this
|
||||||
e.g., using an existing port as the base for a
|
should only be done when it is really needed
|
||||||
very similar program with a different name, or
|
— e.g., using an existing port as the base
|
||||||
upgrading a port to a new upstream version which
|
for a very similar program with a different
|
||||||
actually changes the distribution name, like the
|
name, or upgrading a port to a new upstream
|
||||||
transition from
|
version which actually changes the distribution
|
||||||
|
name, like the transition from
|
||||||
<filename>textproc/libxml</filename> to
|
<filename>textproc/libxml</filename> to
|
||||||
<filename>textproc/libxml2</filename>. In most
|
<filename>textproc/libxml2</filename>. In most
|
||||||
cases, changing <varname>LATEST_LINK</varname>
|
cases, adding or changing
|
||||||
should suffice.</para>
|
<varname>PKGNAMEPREFIX</varname> or
|
||||||
|
<varname>PKGNAMESUFFIX</varname> should
|
||||||
|
suffice.</para>
|
||||||
</step>
|
</step>
|
||||||
|
|
||||||
<step>
|
<step>
|
||||||
|
|
|
@ -1238,41 +1238,6 @@ PORTEPOCH= 1</programlisting>
|
||||||
them part of <varname>PORTNAME</varname>.</para>
|
them part of <varname>PORTNAME</varname>.</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2>
|
|
||||||
<title><varname>LATEST_LINK</varname></title>
|
|
||||||
|
|
||||||
<para><varname>LATEST_LINK</varname> is used during package
|
|
||||||
building to determine a shortened name to create links that
|
|
||||||
can be used by <command>pkg_add -r</command>. This makes it
|
|
||||||
possible to, for example, install the latest perl version by
|
|
||||||
running <command>pkg_add -r perl</command> without knowing
|
|
||||||
the exact version number. This name needs to be unique and
|
|
||||||
obvious to users.</para>
|
|
||||||
|
|
||||||
<para>In some cases, several versions of a program may be
|
|
||||||
present in the ports collection at the same time. Both the
|
|
||||||
index build and the package build system need to be able to
|
|
||||||
see them as different, independent ports, although they may
|
|
||||||
all have the same <varname>PORTNAME</varname>,
|
|
||||||
<varname>PKGNAMEPREFIX</varname>, and even
|
|
||||||
<varname>PKGNAMESUFFIX</varname>. In those cases, the
|
|
||||||
optional <varname>LATEST_LINK</varname> variable should be
|
|
||||||
set to a different value for all ports except the
|
|
||||||
<quote>main</quote> one — see the
|
|
||||||
<filename>lang/gcc46</filename> and
|
|
||||||
<filename>lang/gcc</filename> ports, and the
|
|
||||||
<filename>www/apache*</filename> family for examples of its
|
|
||||||
use. By setting <varname>NO_LATEST_LINK</varname>, no link
|
|
||||||
will be generated, which may be an option for all but the
|
|
||||||
<quote>main</quote> version. Note that how to choose a
|
|
||||||
<quote>main</quote> version —
|
|
||||||
<quote>most popular</quote>, <quote>best supported</quote>,
|
|
||||||
<quote>least patched</quote>, and so on — is outside
|
|
||||||
the scope of this handbook's recommendations; we only tell
|
|
||||||
you how to specify the other ports' versions after you have
|
|
||||||
picked a <quote>main</quote> one.</para>
|
|
||||||
</sect2>
|
|
||||||
|
|
||||||
<sect2 xml:id="porting-pkgname">
|
<sect2 xml:id="porting-pkgname">
|
||||||
<title>Package Naming Conventions</title>
|
<title>Package Naming Conventions</title>
|
||||||
|
|
||||||
|
@ -1341,9 +1306,8 @@ PORTEPOCH= 1</programlisting>
|
||||||
<varname>PORTNAME</varname>, as the
|
<varname>PORTNAME</varname>, as the
|
||||||
<filename>www/apache*</filename> ports do; in that case,
|
<filename>www/apache*</filename> ports do; in that case,
|
||||||
different versions (and different index entries) are
|
different versions (and different index entries) are
|
||||||
distinguished by the <varname>PKGNAMEPREFIX</varname>,
|
distinguished by the <varname>PKGNAMEPREFIX</varname>
|
||||||
<varname>PKGNAMESUFFIX</varname>, and
|
and <varname>PKGNAMESUFFIX</varname> values.</para>
|
||||||
<varname>LATEST_LINK</varname> values.</para>
|
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
|
|
|
@ -153,14 +153,6 @@ two main categories:
|
||||||
the port. (This email is not automated but it should be sent
|
the port. (This email is not automated but it should be sent
|
||||||
as a courtesy.)</p></li>
|
as a courtesy.)</p></li>
|
||||||
|
|
||||||
<li><p>a list of ports that do not set NO_LATEST_LINK. (Ports
|
|
||||||
that have a stable version, and a development version, will
|
|
||||||
generally have the development version set to a later revision.
|
|
||||||
If it is desirable that users should install the stable version
|
|
||||||
from packages, rather than the development version, this flag
|
|
||||||
should be set; otherwise, users will get the latest version by
|
|
||||||
default.)</p></li>
|
|
||||||
|
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
</li>
|
</li>
|
||||||
|
|
Loading…
Reference in a new issue