| Line 64... |
Line 64... |
| 64 |
PROGS | User programs, tools...
|
64 |
PROGS | User programs, tools...
|
| 65 |
|
65 |
|
| 66 |
Note: "DOC", "NLS", "BIN" and "HELP" directories are strictly reserved to
|
66 |
Note: "DOC", "NLS", "BIN" and "HELP" directories are strictly reserved to
|
| 67 |
CORE packages.
|
67 |
CORE packages.
|
| 68 |
|
68 |
|
| - |
|
69 |
|
| 69 |
%hLSM meta-data files
|
70 |
%hLSM meta-data files
|
| 70 |
|
71 |
|
| 71 |
Every package MUST contain an LSM file in its "APPINFO" directory. This LSM
|
72 |
Every package MUST contain an LSM file in its "APPINFO" directory. This LSM
|
| 72 |
file is a text file that contains basic information about the package. Its
|
73 |
file is a text file that contains basic information about the package. Its
|
| 73 |
format is very simple, it must contain at least two lines:
|
74 |
format is very simple, it must contain at least two lines:
|
| 74 |
|
75 |
|
| 75 |
version: x.y.z
|
76 |
version: x.y.z
|
| 76 |
description: package description
|
77 |
description: package description
|
| 77 |
|
78 |
|
| 78 |
Any other lines are ignored by the SvarDOS package manager.
|
79 |
Any other lines are ignored by the SvarDOS package manager.
|
| - |
|
80 |
|
| - |
|
81 |
|
| - |
|
82 |
%hPackage versions
|
| - |
|
83 |
|
| - |
|
84 |
The version present in the LSM file is meant to reflect the version of the
|
| - |
|
85 |
packaged software, but it may happen that a package needs to be changed to
|
| - |
|
86 |
fix a strictly packaging-related issue (for example a forgotten documentation
|
| - |
|
87 |
file or a recompilation of the binary using a better set of flags...). In such
|
| - |
|
88 |
case, the version of the software does not change, but the version of the
|
| - |
|
89 |
package itself needs to change so users know something changed. That's what
|
| - |
|
90 |
"SvarDOS revisions" come in. A version string is basically following such
|
| - |
|
91 |
format:
|
| - |
|
92 |
|
| - |
|
93 |
UPSTREAM_VER[+SVARREV]
|
| - |
|
94 |
|
| - |
|
95 |
UPSTREAM_VER is the exact version string advertised by the software. It may
|
| - |
|
96 |
be pretty much anything. This upstream version may be optionally followed by a
|
| - |
|
97 |
plus sign and the SvarDOS revision. In the even that the upstream version
|
| - |
|
98 |
already contains a plus sign, then SvarDOS revision is delimited with a tilde.
|
| - |
|
99 |
|
| - |
|
100 |
The SvarDOS revision starts at 0 and increments each time that the given
|
| - |
|
101 |
upstream revision is repackaged. The SvarDOS revision restarts whenever the
|
| - |
|
102 |
upstream version changes. The SvarDOS revision of 0 is always hidden.
|
| - |
|
103 |
|
| - |
|
104 |
Examples:
|
| - |
|
105 |
|
| - |
|
106 |
FDISK 1.54 <- originally packaged version
|
| - |
|
107 |
FDISK 1.54+1 <- package has been changed, but not the upstream version
|
| - |
|
108 |
FDISK 1.55 <- upstream version increased, so SvarDOS rev restarts
|
| - |
|
109 |
FDISK 1.55+1 <- new version of the package, but still contains FDISK 1.55
|
| - |
|
110 |
FDISK 1.55+2 <- another new version of the package, etc
|