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

Use of quote tags, addition of some literal tags and —

Browse source
This commit is contained in:
Marc Fonvieille 2002-09-15 15:54:55 +00:00
parent 15e39b7251
commit 4c5c688d5f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=14286
1 changed files with 8 additions and 8 deletions

16
en_US.ISO8859-1/books/porters-handbook/book.sgml
View file

@ -845,7 +845,7 @@ lib/X11/oneko/mouse.xpm
numerically less than the previous version (20000801), but numerically less than the previous version (20000801), but
the <literal>,1</literal> suffix is treated specially by the <literal>,1</literal> suffix is treated specially by
automated tools and found to be greater than the implied automated tools and found to be greater than the implied
suffix ",0" on the earlier package.</para> suffix <literal>,0</literal> on the earlier package.</para>
<para>It is expected that <makevar>PORTEPOCH</makevar> will <para>It is expected that <makevar>PORTEPOCH</makevar> will
not be used for the majority of ports, and that sensible not be used for the majority of ports, and that sensible
@ -853,10 +853,10 @@ lib/X11/oneko/mouse.xpm
it becoming necessary if a future release of the software it becoming necessary if a future release of the software
should change the version structure. However, care is should change the version structure. However, care is
needed by FreeBSD porters when a vendor release is made needed by FreeBSD porters when a vendor release is made
without an official version number - such as a code without an official version number &mdash; such as a code
"snapshot" release. The temptation is to label the <quote>snapshot</quote> release. The temptation is to label the
release with the release date, which will cause problems release with the release date, which will cause problems
as in the example above when a new "official" release is as in the example above when a new <quote>official</quote> release is
made.</para> made.</para>
<para>For example, if a snapshot release is made on the date <para>For example, if a snapshot release is made on the date
@ -891,7 +891,7 @@ PORTREVISION= 1</programlisting>
<para><makevar>PKGNAME</makevar> becomes <para><makevar>PKGNAME</makevar> becomes
<literal>gtkmumble-0.10_1</literal></para> <literal>gtkmumble-0.10_1</literal></para>
<para>A new version is released by the vendor, numbered 0.2 <para>A new version is released by the vendor, numbered <literal>0.2</literal>
(it turns out the author actually intended (it turns out the author actually intended
<literal>0.10</literal> to actually mean <literal>0.10</literal> to actually mean
<literal>0.1.0</literal>, not <quote>what comes after <literal>0.1.0</literal>, not <quote>what comes after
@ -899,7 +899,7 @@ PORTREVISION= 1</programlisting>
version <literal>2</literal> is numerically less than the version <literal>2</literal> is numerically less than the
previous version <literal>10</literal> the previous version <literal>10</literal> the
<makevar>PORTEPOCH</makevar> must be bumped to manually <makevar>PORTEPOCH</makevar> must be bumped to manually
force the new package to be detected as "newer". Since it force the new package to be detected as <quote>newer</quote>. Since it
is a new vendor release of the code, is a new vendor release of the code,
<makevar>PORTREVISION</makevar> is reset to 0 (or removed <makevar>PORTREVISION</makevar> is reset to 0 (or removed
from the makefile).</para> from the makefile).</para>
@ -1022,10 +1022,10 @@ PORTEPOCH= 1</programlisting>
integers and single lowercase alphabetics. In particular, integers and single lowercase alphabetics. In particular,
it is not permissible to have another dash inside the it is not permissible to have another dash inside the
version string. The only exception is the string version string. The only exception is the string
<literal>pl</literal> (meaning `patchlevel'), which can be <literal>pl</literal> (meaning <quote>patchlevel</quote>), which can be
used <emphasis>only</emphasis> when there are no major and used <emphasis>only</emphasis> when there are no major and
minor version numbers in the software. If the software minor version numbers in the software. If the software
version has strings like "alpha", "beta", "rc", or "pre", take version has strings like <quote>alpha</quote>, <quote>beta</quote>, <quote>rc</quote>, or <quote>pre</quote>, take
the first letter and put it immediately after a period. the first letter and put it immediately after a period.
If the version string continues after those names, the If the version string continues after those names, the
numbers should follow the single alphabet without an extra numbers should follow the single alphabet without an extra