Last modified: 29 Aug 2007
WARNING: This documentation covers Parallels H-Sphere versions up to 3.1. For the latest up-to-date Parallels H-Sphere documentation, please proceed to the
official Parallels site.
For each application you want to package via EasyApp SDK, you need to create a descriptor. Inside application
directory create main.xml. The file starts with app tag.
There are several tags inside:
||the name of the project (alphanumeric), will be used as resource type in h-sphere
|description||will be used as resource description
||label to use as a title of the application
||label to use as basic decription/intro for the app
||name of the tarball/bundle within the application. File under the same name should be in application
|size||disk space that script requires, in MB
|license||attribute type="XXX" - specifies the license type, value specifies URL to the
license. If known type is used, no url is necessary. Known types: GPL", "BSD", "MPL"
||url to application homepage
|donation||url to donation page
|documentation||url to documentation page
|forum||url to support forum
||image name - logo image, should be present in the application directory
||list of configurational parameters/variables user will be prompted with during install/or when he wants to
|| list of actions to perform during the installation of
application; it can contain optional done tag that describes actions performed at the end of the installation, if any. It can
include other tags:
- iframe - link to the original installation page the user will be taken to at some stage of the installation. You can use
this tag if it's too complicated to perform the entire procedure in H-Sphere.
- access - gives link to application or its parts the user will be taken to after the installation is finished, e.g. page of
the application's administrator.
||list of actions to perform on change
||list of actions to perform on uninstall
||attribute from="XXX" - where XXX is previously defined version. There can be multiple upgrade tags,
from different versions. Inside upgrade tag, there is actions tag for actions to perform during upgrade. The tag is
used to automate upgrades of the application
||language files bundled with package.
- Section <lang> - Specifies which lang file must be used for this application
- Sections <install>,<remove> - Describes the actions that constitute install/uninstall of the
- Section <upgrade> - Used for possible autoupgrades, just like in <install>, <uninstall>,
and <change>, but in the title requries the number of the version you upgrade from.
Here is an example of descriptor for Mambo