Open main menu

Changes

Packages.xml

715 bytes added, 07:31, 27 July 2010
added advanced formats to revision, so we can get rid of people thinking only integers are supported
[http://wpkg.org WPKG] will not work without this file.
 
==packages.xml structure==
</packages>
</source>
 
Each package has the following attributes:
* '''name''' - longer textual description of the package. This should be the full product name.
* '''revision''' - user created integer version number to represent the "version" of the specific WPKG package for this application. Should be incremented when creating a new releaseIf you change the package, increment it. Not to It can be confused with the software application's version or revision that the WPKG package is for.** The following formats are supported:*** an integer (1, 10, 1000, etc.)*** dotted revision numbers (1.1, 2.1.4, 3.200.3987, etc.) ... introduced with WPKG 1.0*** volatile revisions (1.2RC1, 1.5I32, 2.73M24, 1.65.b, etc.) ... introduced with WPKG 1.1.1** If you like to keep track of the date you have last changed the package, since there is no better revision number, you can use the format YYYY.MM.DD (2010.07.27, etc.)** In addition one can define a variable inside the package and use that as the revision (introduced with WPKG 1.1.2):<source lang="xml"><package id="firefox" name="Mozilla Firefox" revision="%PKG_VERSION%" reboot="false" priority="10">  <variable name="PKG_VERSION" value="3.6.8" /></source>
* '''reboot''' - specifies if and how the system reboots when installing, removing or upgrading a given package.
== Check conditions / check type ==
 
Of course it would be unwise to launch the installer if the software is already installed. That's why there are "check conditions".
Check conditions are broken down into 4 categories:
 
<ul>
<li>'''Execute''' - Executes a script and checks the returning errorlevel (since WPKG 1.1.0)
</ul>
 
'''Registry'''