Ticket #80: hints.diff
| File hints.diff, 4.0 kB (added by Jan-Nik, 7 months ago) |
|---|
-
doc/root_names
old new 3 3 Definitions 4 4 ----------- 5 5 6 Package: An Autopackage .package file.7 Software: The software itself.6 Package: An Autopackage .package file. 7 Software: The software itself. 8 8 9 9 10 10 What is a root name? … … 139 139 number or a package version number. So: 140 140 141 141 require "@gtk.org/gtk" 1 # valid 142 require "@gtk.org/gtk" 1.2 # valid142 require "@gtk.org/gtk" 1.2 # valid 143 143 require "@gtk.org/gtk:2.0.0:1" 1 # invalid 144 144 145 145 MAJOR and REVISION are of course the required major and revision numbers. … … 202 202 203 203 ROOTNAME may or may not contain a software version number. 204 204 If it does: 205 MAJOR and REVISION are ignored.206 Search the harddisk and network for a packages that matches the given207 version number. Out of those packages, select the one with the highest208 package number.205 MAJOR and REVISION are ignored. 206 Search the harddisk and network for a packages that matches the given 207 version number. Out of those packages, select the one with the highest 208 package number. 209 209 If it doesn't: 210 MAJOR will be a required parameter and REVISION an optional one.211 1. Search the harddisk and network for packages that match MAJOR.212 If REVISION is specified:213 1.1. Out of those packages, select the ones with a revision214 version number that is equal or higher than REVISION.215 Then select the ones with the highest REVISION number.216 2. Select the ones with the highest software number.217 3. Select the ones with the highest package number.210 MAJOR will be a required parameter and REVISION an optional one. 211 1. Search the harddisk and network for packages that match MAJOR. 212 If REVISION is specified: 213 1.1. Out of those packages, select the ones with a revision 214 version number that is equal or higher than REVISION. 215 Then select the ones with the highest REVISION number. 216 2. Select the ones with the highest software number. 217 3. Select the ones with the highest package number. 218 218 219 219 220 220 Example: … … 263 263 ------- 264 264 Are you confused with all the different version numbers? We have: 265 265 266 Software version: The version number of the software, as defined by the267 maintainer. Tends to be put on websites etc266 Software version: The version number of the software, as defined by the 267 maintainer. Tends to be put on websites etc 268 268 269 Package version: The number of the package. Similar to RPM's Release270 number. Used only in the specfile. Used for "bugfix271 releases" of a package itself.269 Package version: The number of the package. Similar to RPM's Release 270 number. Used only in the specfile. Used for "bugfix 271 releases" of a package itself. 272 272 273 Interface version: Version number used to determine the interface274 compatibility of the software.275 + Major276 + Revision273 Interface version: Version number used to determine the interface 274 compatibility of the software. 275 + Major 276 + Revision -
doc/DEVELOPER-HINTS
old new 77 77 78 78 main/doc/api - automatically generated API documentation 79 79 main/doc - general doc files 80 main/make installer- the script that builds .package files80 main/makepackage - the script that builds .package files 81 81 main/share/apkg-ttyfe - the terminal frontend program 82 82 main/share/apkg-funclib - general functions that don't fit anywhere else, and the file you import to get all the rest of the code 83 83 main/share/apkg-script-utils - the bulk of the public API, these functions are meant to be used from prep and install scripts … … 127 127 128 128 For more information on this, see the document main/doc/root_names 129 129 130 131
