Copyright © 2005 Robert Bienert
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License.
Abstract
This section describes how to "read" a given LayManSys version number, because this number tells us a lot about the package numbered this way. The section covers information about major, minor and bugfix releases as well as stable and development packages.
LayManSys uses the so-called Linux Kernel Versioning System, that means, if you have a certain release number, you can see directly, if the package is a stable or a development one. This versioning system is not difficult to understand: A version number consists of three numbers, each delimited by a dot . They are ordered by major version, minor version and patch level, e.g.
where M means the major number, m stands for the minor number and p is the patch level. All three numbers have at least one digit, so
is a valid version number.
The Linux Kernel Versioning System also differs between stable and (maybe unstable) development releases. Stable versions, that are made for production systems have an even minor version number, development packages an odd one.
LayManSys consists of several packages that are developed independently from each other. To show you which packages work or belong together, you only need to have a look at the major and minor version numbers: If they are the same, both packages work together. The patch level, as stated by the name patch level only helps to find the latest, patched release. To make things clear, guess you have to following two packages downloaded:
Example 3. Two Packages with Matching Version Number
laymansys-library-0.1.0.zip laymansys-demo-0.1.1.zip
Take their major and minor version numbers, which is in both cases 0.1 and compare them: In this case, they are the same, that means, both packages work together. But in the following example, you may get into trouble when using LayManSys:
Example 4. Two Packages with Version Numbers not Matching
laymansys-library-0.2.0.zip laymansys-demo-0.1.1.zip
The reason for your possible problems is easy: Take their relevant version numbers 0.2 and 0.1 and compare them, but this time, they are not equal.
With the information above in your mind, you can now go to the LayManSys Download Page for getting the latest release. The next chapters describe, how to setup up a working LayManSys installation and how to customize it for your needs.
Each LayManSys release can also be found in the CVS repository; the releases are tagged using the following schemata:
Version_M_m_p, e.g.
Beta_YYYY_MM_DD, where YYYY stands for the year, MM for the month and DD is the release day, e.g.
PACKAGE_M_m_p, where PACKAGE stands for the (CVS) package with a starting uppercase character, e.g. there is a release tagged
The word before the first underscore is written exactly like this, while M_m_p is the release number as described above.
You can view the CVS repository using SourceForge.net's ViewCVS service at http://laymansys.cvs.sourceforge.net/laymansys/.