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

Describe and recommend the use of the LATEST_LINK variable in

Browse source 
the Committer's Guide ports repo-copy section and in the package naming
section of the Porter's Handbook.  In the end, I wrote something that
turned out quite a bit different and somewhat more long-winded than
the suggestions in the PR, but LATEST_LINK was not documented anywhere
until now, so there :)

PR:		66775
Submitted by:	eik
This commit is contained in:
Peter Pentchev 2007-04-25 13:13:22 +00:00
parent 444f23be02
commit be122238a0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=30088
2 changed files with 62 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

24
en_US.ISO8859-1/articles/committers-guide/article.sgml
View file

@ -731,11 +731,11 @@ alias scvs cvs -d <replaceable>user</replaceable>@ncvs.FreeBSD.org:/home/ncvs</p
</itemizedlist>
<para>You will almost certainly get a conflict because
of the <literal>$Id: article.sgml,v 1.260 2007-04-08 17:45:24 blackend Exp $</literal> (or in FreeBSD's case,
of the <literal>$Id: article.sgml,v 1.261 2007-04-25 13:13:22 roam Exp $</literal> (or in FreeBSD's case,
<literal>$<!-- stop expansion -->FreeBSD<!-- stop expansion -->$</literal>)
lines, so you will have to edit the file to resolve the conflict
(remove the marker lines and the second <literal>$Id: article.sgml,v 1.260 2007-04-08 17:45:24 blackend Exp $</literal> line,
leaving the original <literal>$Id: article.sgml,v 1.260 2007-04-08 17:45:24 blackend Exp $</literal> line intact).</para>
(remove the marker lines and the second <literal>$Id: article.sgml,v 1.261 2007-04-25 13:13:22 roam Exp $</literal> line,
leaving the original <literal>$Id: article.sgml,v 1.261 2007-04-25 13:13:22 roam Exp $</literal> line intact).</para>
</listitem>
<listitem>
@ -2547,9 +2547,21 @@ docs:Documentation Bug:freebsd-doc:</programlisting>
<procedure>
<step>
<para>Upgrade the copied port to the new version (remember
to change the <makevar>PORTNAME</makevar> so there
are not duplicate ports with the same name).</para>
<para>Upgrade the copied port to the new version.
Remember to change the <makevar>LATEST_LINK</makevar>
so there are no duplicate ports with the same name.
In some rare cases it may be necessary to change the
<makevar>PORTNAME</makevar> instead of
<makevar>LATEST_LINK</makevar>, 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 <makevar>LATEST_LINK</makevar> should
suffice.</para>
</step>
<step>