Application Package Specification (Idea)
This specification is designed to provide a desktop neutral way to package one application.
Dependencies can be installed on first start of the application. The necessary runtime environment should be installed (may use of packagekit) and the runtime environment should install the necessary modules.
A application-package is an archive containing the application and a file describing all the contents. The archive should be a gzip-compressed tarball with an .app extension.
/ /info /app/
The info file should be formatted as followed:
[Application] Name=Example application
The Name of the application, it is required for identification-purposes.
The Desktop-file syntax version, this field must be present.
The mime-type, this field must be present and have the value X-ApplicationPackage.
This field represents the main executable file of the application. It must be present.
Mime-type of executable file
This field represents the mime-type of the main executable file of the application. It must be present.
Maintainer=John Doe <john DOT doe AT freedesktop DOT org>
The ThemePackage maintainer, this field should be present and formatted as followed
_Name < email >_
If for some reason this field is not available, implementations may choose to warn a user about this fact.
The ApplicationPackage version-number (increases with every update), this field should be present and formatted as followed
Where a, b, c, d and e are numbers between 0 and 4294967296 (32 bits unsigned integers).
Author(s) / Artist(s) name(s)
Authors=Jane Doe <jane AT freedesktop DOT org>; John Doe <john AT freedesktop DOT org>
The author(s) of the application, this field may be present.
_Name < email >[; Name < email >[; etc...]]_
Description=This example application is a great multiplayer game for the whole family. You can use your keyboard and your mouse. For more information see our website: www.greatgame.example.
This field provides a description about the application.
Application License Information
The License under which the application is distributed.
Icon to display in the software center, menus, etc. The name of the file should be either an web address or a name according to the Icon Theme Specification.
Web address for download
The web address which allows to download the application again.
An info file according to this spec. This file must content an DownloadURL field. It should provide a never version if available. This specification allows to put information about several versions in one info file.
[Application] Name=Example application Version=1.0 Type=X-ApplicationPackage Exec=example.bin ExecType=application/x-executable Maintainer=John Doe <john AT freedesktop DOT org> Application-Version=1.0 Authors=Jane Doe <jane AT freedesktop DOT org>; John Doe <john AT freedesktop DOT org> Description=This example application is a great multiplayer game for the whole family. You can use your keyboard and your mouse. For more information see our website: www.greatgame.example. License=GPL;Creative-Commons Icon=http://example.com/example_app_icon.svg DownloadURL=http://example.com/example.app UpdateInfo=http://example.com/example.info
This directory contains the application files. This directory will be used to look for the exec file which is stated in the info file.
The user should be able to copy the application to applications:// to register the application. At all you don't need to install the application, just execute the app-file to use the application. The system will may share the application for multiple users.
Software according to this specification should run in a sandbox. The application is not allowed to read any personal information from the home directory. Therefore eachgets his own home directory with write access. A special file selector widget should allow applications to read and write to specific files chosen by the user.
The package server should be able to provide descriptions of packages in the user's language.