| Line 44... |
Line 44... |
| 44 |
in it. Great! To upload it to the SvarDOS online repo, copy your zip package
|
44 |
in it. Great! To upload it to the SvarDOS online repo, copy your zip package
|
| 45 |
to your local svardos-packages directory. Then, instruct svn to add the new
|
45 |
to your local svardos-packages directory. Then, instruct svn to add the new
|
| 46 |
file(s) to the repo:
|
46 |
file(s) to the repo:
|
| 47 |
|
47 |
|
| 48 |
$ cd svardos-packages
|
48 |
$ cd svardos-packages
|
| 49 |
$ svn add package.svp
|
49 |
$ svn add package-ver.svp
|
| 50 |
$ svn add package.zip <-- optional, only if the package has available sources
|
50 |
$ svn add package-ver.zip <-- optional, only if package has available sources
|
| 51 |
|
51 |
|
| 52 |
Review the changes to make sure you added the right files:
|
52 |
Review the changes to make sure you added the right files:
|
| 53 |
$ svn st
|
53 |
$ svn st
|
| 54 |
|
54 |
|
| 55 |
...and if everything's all right, push (commit) the changes to the svn server:
|
55 |
...and if everything's all right, push (commit) the changes to the svn server:
|
| Line 61... |
Line 61... |
| 61 |
|
61 |
|
| 62 |
|
62 |
|
| 63 |
=== UPDATING A PACKAGE (ADD A NEW VERSION) ====================================
|
63 |
=== UPDATING A PACKAGE (ADD A NEW VERSION) ====================================
|
| 64 |
|
64 |
|
| 65 |
Let's imagine that we have a package named NASM in version 2.12. A new version
|
65 |
Let's imagine that we have a package named NASM in version 2.12. A new version
|
| 66 |
of this software has been released, you tested it, found it stable so you
|
66 |
2.15 of this software has been released, you tested it, found it stable so you
|
| 67 |
packaged it. How to add it to the SvarDOS packages repository?
|
67 |
packaged it. How to add it to the SvarDOS packages repository?
|
| 68 |
|
68 |
|
| 69 |
First, you need to rename the current package's filename so it becomes an
|
- |
|
| 70 |
"alternative version":
|
69 |
Add the new version of your package:
|
| 71 |
|
70 |
|
| 72 |
$ cd svardos-packages
|
- |
|
| 73 |
$ svn mv nasm.svp nasm-2.12.svp
|
- |
|
| 74 |
$ svn mv nasm.zip nasm-2.12.zip <-- optional (only if package has sources)
|
- |
|
| 75 |
|
- |
|
| 76 |
Then, add the new version as the "current" version:
|
- |
|
| 77 |
|
- |
|
| 78 |
$ svn add nasm.svp
|
71 |
$ svn add nasm-2.15.svp
|
| 79 |
$ svn add nasm.zip <-- optional (only if package has sources)
|
72 |
$ svn add nasm-2.15.zip <-- optional (only if package has sources)
|
| 80 |
|
73 |
|
| 81 |
Finally, review and commit your changes:
|
74 |
Finally, review and commit your changes:
|
| 82 |
|
75 |
|
| 83 |
$ svn st
|
76 |
$ svn st
|
| 84 |
$ svn commit -m 'updated NASM to version 2.13'
|
77 |
$ svn commit -m 'updated NASM to version 2.15'
|
| - |
|
78 |
|
| - |
|
79 |
The repository server will automatically serve the latest available version as
|
| - |
|
80 |
the "preferred" version to users. The version strings are processed (and
|
| - |
|
81 |
compared with each other) through the PHP version_compare() function documented
|
| - |
|
82 |
here: <https://www.php.net/manual/en/function.version-compare>
|
| - |
|
83 |
|
| - |
|
84 |
This function works relatively well, but it might fail on some exotic version
|
| - |
|
85 |
strings. For the time being, there is no way to flag a specific package version
|
| - |
|
86 |
as being "preferred".
|
| 85 |
|
87 |
|
| 86 |
|
88 |
|
| 87 |
=== REMOVING A PACKAGE ========================================================
|
89 |
=== REMOVING A PACKAGE ========================================================
|
| 88 |
|
90 |
|
| 89 |
On rare occasions it may be necessary to delete some packages. For example if
|
91 |
On rare occasions it may be necessary to delete some packages. For example if
|