Commit 6e5fe866 authored by Emanuele Aina's avatar Emanuele Aina

applications: Use "metadata" instead of "meta-data"

Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>

Differential Revision: https://phabricator.apertis.org/D4015
parent 81b46f82
......@@ -223,7 +223,7 @@ decide on based on what makes more sense for the application.
The application store will be responsible for packaging a developer's
store application bundle into a bundle file along with a “store
directory”(see [](#store-directory)) that contains some generated
meta-data and a signature. Special “SDK” system images will provide
metadata and a signature. Special “SDK” system images will provide
software development tools and allow the installation of unsigned
packages, but the normal “target” system image will not allow the
installation of packages that don't contain a valid store signature.
......@@ -247,7 +247,7 @@ experience significant pressure at these times.
In order for the the application update system to work properly, each
new release of an application needs to have a version number greater
than the previous release. The store may need to make changes to
application meta-data between the developer's releases of that
application metadata between the developer's releases of that
application. To allow the store to increment the application version
without interfering with the developer's version numbers, the store will
maintain a “store version” number to be appended to the developer's
......@@ -1023,7 +1023,7 @@ services, handlers, or launchable components of the application until
the final phase of installation is complete.
It is possible that the application store will push a version that
changes only the application meta-data (the store version changes, but
changes only the application metadata (the store version changes, but
the application version does not). This will result in a simplified
upgrade process.
......@@ -1868,7 +1868,7 @@ directory, and will not contain any special per-user files.
## Anatomy of an Application bundle
Store applications are distributed as bundles that contain an
application and a directory full of store meta-data. Built-in
application and a directory full of store metadata. Built-in
applications will be further packaged into .deb files to be pushed
through the system upgrade infrastructure.
......@@ -1959,7 +1959,7 @@ application may look like:
### Store Directory
The store directory contains store generated meta-data: a secure hash
The store directory contains store generated metadata: a secure hash
file (store.json), a signature (store.sig) generated by gpg using the
application store's private key, and an AppArmor file containing
profiles for each executable in the application.
......@@ -1995,7 +1995,7 @@ external media.
### The Manifest
The manifest is a JSON format file that aggregates application meta-data
The manifest is a JSON format file that aggregates application metadata
into a single convenient file for developers – The following snippet provides an
example. Some of the information will be used to determine if the
application is installable or not, other sections will be parsed by the
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment