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

Remove LATEST_LINK mentions, nobody should use it, ever.

Browse source 
Sponsored by:	Absolight
This commit is contained in:
Mathieu Arnold 2014-02-04 14:09:02 +00:00
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
Download patch file Download diff file Expand all files Collapse all files

28
en_US.ISO8859-1/articles/committers-guide/article.xml
View file

@ -4014,22 +4014,26 @@ MFC after: 1 month</programlisting>
<step>
<para>Upgrade the copied port to the new version.
Remember to change the
<varname>LATEST_LINK</varname> so there are no
Remember to add or change the
<varname>PKGNAMEPREFIX</varname> or
<varname>PKGNAMESUFFIX</varname> so there are no
duplicate ports with the same name. In some
rare cases it may be necessary to change the
<varname>PORTNAME</varname> instead of
<varname>LATEST_LINK</varname>, but this should
only be done when it is really needed &mdash;
e.g., using an existing port as the base for a
very similar program with a different name, or
upgrading a port to a new upstream version which
actually changes the distribution name, like the
transition from
<varname>PORTNAME</varname> instead of adding
<varname>PKGNAMEPREFIX</varname> or
<varname>PKGNAMESUFFIX</varname>, but this
should only be done when it is really needed
&mdash; e.g., using an existing port as the base
for a very similar program with a different
name, or upgrading a port to a new upstream
version which actually changes the distribution
name, like the transition from
<filename>textproc/libxml</filename> to
<filename>textproc/libxml2</filename>. In most
cases, changing <varname>LATEST_LINK</varname>
should suffice.</para>
cases, adding or changing
<varname>PKGNAMEPREFIX</varname> or
<varname>PKGNAMESUFFIX</varname> should
suffice.</para>
</step>
<step>