From b8e83cb34481b19b268e5df2f3db21e0328468a6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Eray=20=C3=96zkural?= Date: Tue, 27 Sep 2005 17:08:01 +0000 Subject: [PATCH] * some minor corrections --- doc/package_versions.tex | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/package_versions.tex b/doc/package_versions.tex index 829e3738..6d214ed4 100644 --- a/doc/package_versions.tex +++ b/doc/package_versions.tex @@ -16,12 +16,12 @@ packages. Source version is the version number provided is provided by the upstream maintainer of the source archive used in package. It must be -allways the same with the upstream version used. +always the same as the upstream version used. \textbf{Example}: If the upstream archive name is \emph{bash-3.0.tar.gz} the version number of the package is \emph{3.0} -\subsection{Version Prefix} +\subsection{Version Suffixes} There is a pre-defined list of suffixes a package version can take. @@ -30,13 +30,13 @@ take. \item \textbf{alpha} Source/Package is in alpha state \item \textbf{beta} Source/Package is in beta state \item \textbf{pre} Source/Pacgage passed the beta state but stable - version isn't relased yet. + version is not relased yet. \item \textbf{rc} Source/Package is a release-candidate. \item \textbf{p} Source/Package is released and some patches are applied after the release. This is the patch level. \end{itemize} -The suffix should be written after the special seperator +The suffix should be written after the special separator character \textbf{\_}. And there must allways be a number after a suffix. \textbf{Example}: packagename-1.0\_beta1