docs/66775: Clarification that port names should not contain version numbers

[Oliver Eikemeier]

Aasmund Eikli wrote:

>  Doc diffs to reflect suggestions:
>
>  --- article.sgml        Tue Jul 27 16:34:49 2004
>  +++ article.sgml        Sat Jul 31 15:35:56 2004
>  @@ -2418,7 +2418,9 @@
>                     <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>
>  +                     are not duplicate ports with the same name).
>  +                     Alternatively, change 
> <makevar>LATEST_LINK</makevar>
>  +                     depending on the purpose.</para>
>                     </step>
>
>                     <step>

I would prefer suggesting to change LATEST_LINK only, and PORTNAME only 
in rare cases. The reader might get the impression that `apache-1.3' 
and `apache-2.0' have the same name, although they don't.


>  --- book.sgml   Sat Jul 31 15:40:21 2004
>  +++ book.sgml   Sat Jul 31 15:52:11 2004
>  @@ -1064,7 +1064,10 @@
>               <literal>Data::Dumper</literal> module becomes
>               <literal>p5-Data-Dumper</literal>.  If the software in 
> question
>               has numbers, hyphens, or underscores in its name, you may
>  include
>  -           them as well (like <literal>kinput2</literal>).</para>
>  +           them as well (like <literal>kinput2</literal>).
>  +           Make sure that the <makevar>PORTNAME</makevar> variable 
> and the
>  +           <makevar>PORTVERSION</makevar> variable contains the name
>  and the
>  +           version number of the port respectively. You should not mix
>  the two.</para>
>           </listitem>

Same here. Perhaps `The version number should not be part of PORTNAME 
(like apache-2.0), except when the original distribution explicitly name 
it that way (like libxml2-2.6).'

-Oliver