ApplicationId

Differences between revisions 6 and 7
⇤ ← Revision 6 as of 2013-09-18 16:55:46 →
Size: 1085
Editor: jdstrand
Comment:
← Revision 7 as of 2013-09-18 17:11:51 → ⇥
Size: 1688
Editor: jdstrand
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * Click
Line 14: Line 15:
|| || filesystem || store || apparmor || deb || intersection ||
|| click_package || [^\0/]+ || [a-zA-Z0-9.-]+ || [a-zA-Z0-9+.:~-]+ || [a-z0-9][a-z0-9+.-]+ || [a-z0-9][a-z0-9.-]+ ||
|| application || [^\0/]+ || || [a-zA-Z0-9+.:~-]+ ||                        || [a-zA-Z0-9+.:~-]+ ||
|| version || [^\0/]+ || [0-9.]+ || [a-zA-Z0-9+.:~-]+ || [0-9][a-zA-Z0-9.+:~-]* || [0-9][0-9.]* ||		 || || filesystem || store || apparmor || deb    || intersection ||
|| click_package || [^\0/]+ || [a-zA-Z0-9.-]+ || [a-zA-Z0-9+.:~-]+ || [a-z0-9][a-z0-9+.-]+^1^ || [a-z0-9][a-z0-9.-]+ ||
|| application || [^\0/]+ || || [a-zA-Z0-9+.:~-]+ || [a-zA-Z0-9+.-]+^2^ || [a-zA-Z0-9+.:~-]+ ||
|| version || [^\0/]+ || [0-9.]+ || [a-zA-Z0-9+.:~-]+ || [0-9][a-zA-Z0-9.+:~-]*^1^ || [0-9][0-9.]* ||
 0. [[http://bazaar.launchpad.net/~click-hackers/click/trunk/view/head:/doc/file-format.rst|click file-format definition]]
 0. [[http://bazaar.launchpad.net/~click-hackers/click/trunk/view/head:/doc/hooks.rst|click hooks definition]]
Line 20: Line 23:

Alternate nomenclatures:
 * 'APP_ID' and `${id}` (from click documentation) is synomymous with 'ApplicationId'
 * 'click package name' ("name" in the click manifest) and 'APP_PKGNAME' is synonymous with $(click_package)
 * 'application name' and 'appname' are synonymous with $(application)
 * 'APP_VERSION' is synonymous with $(version)

The Application ID is the string "$(click_package)_$(application)_$(version)" (without the quotes and with the obvious substitutions made).

This ID is used for identifying the application throughtout the system:

The following restrictions to the components apply, from various parts of the system:

filesystem

store

apparmor

deb

intersection

click_package

[\0/]+ || [a-zA-Z0-9.-]+ || [a-zA-Z0-9+.:~-]+ || [a-z0-9][a-z0-9+.-]+1^

[a-z0-9][a-z0-9.-]+

application

[\0/]+ || || [a-zA-Z0-9+.:~-]+ || [a-zA-Z0-9+.-]+2^

[a-zA-Z0-9+.:]+

version

[\0/]+ || [0-9.]+ || [a-zA-Z0-9+.:~-]+ || [0-9][a-zA-Z0-9.+:~-]*1^

[0-9][0-9.]*

  1. click file-format definition

  2. click hooks definition

Additionally, version should be structured more or less as you would expect, and be strictly monotonically increasing (new versions should always be greater than old versions).

Alternate nomenclatures:

  • 'APP_ID' and ${id} (from click documentation) is synomymous with 'ApplicationId'

  • 'click package name' ("name" in the click manifest) and 'APP_PKGNAME' is synonymous with $(click_package)
  • 'application name' and 'appname' are synonymous with $(application)
  • 'APP_VERSION' is synonymous with $(version)

AppStore/Interfaces/ApplicationId (last edited 2016-06-10 18:13:43 by localhost)