Commit 9d7b3dd9 authored by Simon McVittie's avatar Simon McVittie

Applications: flag app-bundle metadata as merely illustrative

The descriptions of the Store Directory and Manifest seen here
are an illustrative outline of what should go in an app-bundle.
In the 4 years since this section was written, freedesktop.org
specifications for some of this metadata have become widespread;
we should try to align with those to avoid duplicating their work,
as seen in the Application Bundle Metadata design document.

For now, just say so. These sections should be revised when we have
a clear picture of their use cases and requirements. Until then,
we should stick to existing solutions instead of designing new
implementations speculatively.
Reviewed-by: default avatarMathieu Duponchelle <mathieu.duponchelle@opencreed.com>
Signed-off-by: default avatarSimon McVittie <simon.mcvittie@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D4056
parent c062c9f5
......@@ -1880,6 +1880,10 @@ way to require a user to agree to a license.
### Store Directory
> This section has not been updated for current Apertis and should be
> seen as illustrative rather than prescriptive. Its implementation should
> be designed when we have a clearer picture of its use cases and requirements.
The `Application 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
......@@ -1915,6 +1919,10 @@ external media.
### The Manifest
> This section has not been updated for current Apertis and should be
> seen as illustrative rather than prescriptive. Its implementation should
> be designed when we have a clearer picture of its use cases and requirements.
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
......@@ -2076,6 +2084,10 @@ list of the permissions the application would use if allowed.
## **Bundle Specific Metadata**
> This section has not been updated for current Apertis and should be
> seen as illustrative rather than prescriptive. Its implementation should
> be designed when we have a clearer picture of its use cases and requirements.
To simplify the descriptions of installation and update procedures, this
chapter provides the details of application specific metadata (AppArmor
profiles, .desktop files, etc) and how they're handled during
......
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