The 'requirements' key allows to specify the Debian packages which must
be installed and their required version. It must be an array of the
package name as the key and its version specifier - for its format, see
yunohost.utils.packages.Specifier - as value. For example:
"requirements": {
"yunohost": ">= 2.4, << 2.5"
}
It introduces a new `yunohost.utils` package which will contain common
utils used by YunoHost actions. It comes with a work in progress `packages`
module with simple methods to retrieve installed version of packages for now.
The *repository* term is quite new and will replace *app list* in a near
future. It is - for the moment - only shown and used in the Web admin.
This also removes the unused app['manifest']['orphan'] key since it
duplicates the repository absence.
This quickly adds support for git URL with /tree/ inside in app installation.
It is intended to ease tests of apps which use new manifest format and helpers
for the 2.4 release. An example usage:
$ yunohost app install https://github.com/jeromelebleu/roundcube_ynh/tree/dev
As it will certainly change with the app category refactoring, it is not
documented and should be used with care.
The original app_id hard-coded replacement in scripts and hooks is replaced by
the use in app scripts directly of the given app_id argument (wip #126).
It's now the app maintainer responsability to make use of it in a way to
prevent colisions with other instances.
It passes the current app id to the app install/upgrade/remove scripts
as the last argument (wip #126).
The hook category has also been revisited to move some app specific parts
away from there. The action hook_check has been removed accordingly.
