.TP
.B Atom Versions
It is nice to be more specific and say that only certain versions of atoms are
-acceptable. Note that versions must be combined with a prefix (see below). Hence
-you may add a version number as a postfix to the base:
+acceptable. Note that versions must be combined with a prefix (see below).
+Hence you may add a version number as a postfix to the base:
.nf
sys\-apps/sed\fI\-4.0.5\fR
.fi
Versions are normally made up of two or three numbers separated by periods, such
-as 1.2 or 4.5.2. This string may be followed by a character such as 1.2a or 4.5.2z.
-Note that this letter is \fBnot\fR meant to indicate alpha, beta, etc... status.
-For that, use the optional suffix; either _alpha, _beta, _pre (pre\-release), _rc
-(release candidate), or _p (patch). This means for the 3rd pre\-release of a package,
-you would use something like 1.2_pre3.
+as 1.2 or 4.5.2. This string may be followed by a character such as 1.2a or
+4.5.2z. Note that this letter is \fBnot\fR meant to indicate alpha, beta,
+etc... status. For that, use the optional suffix; either _alpha, _beta, _pre
+(pre\-release), _rc (release candidate), or _p (patch). This means for the
+3rd pre\-release of a package, you would use something like 1.2_pre3. The
+suffixes here can be arbitrarily chained without limitation.
.TP
.B Atom Prefix Operators [> >= = <= <]
Sometimes you want to be able to depend on general versions rather than specifying