summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichał Górny <mgorny@gentoo.org>2017-11-13 18:06:27 +0100
committerMichał Górny <mgorny@gentoo.org>2017-11-25 21:49:16 +0100
commit2b932a339cb9a6073e4bc508eaa733dcca1f5fd4 (patch)
treecad91632f0fb19ec5f39540efd4a73ebf3c308eb /glep-0074.rst
parentglep-0074: Clarify timestamp handling of sub-Manifests (diff)
downloadglep-2b932a339cb9a6073e4bc508eaa733dcca1f5fd4.tar.gz
glep-2b932a339cb9a6073e4bc508eaa733dcca1f5fd4.tar.bz2
glep-2b932a339cb9a6073e4bc508eaa733dcca1f5fd4.zip
glep-0074: Explain combining multiple Manifest trees
The idea has been originally suggested by Robin H. Johnson.
Diffstat (limited to 'glep-0074.rst')
-rw-r--r--glep-0074.rst34
1 files changed, 31 insertions, 3 deletions
diff --git a/glep-0074.rst b/glep-0074.rst
index e8fc849..42c0c9e 100644
--- a/glep-0074.rst
+++ b/glep-0074.rst
@@ -8,8 +8,8 @@ Type: Standards Track
Status: Draft
Version: 1
Created: 2017-10-21
-Last-Modified: 2017-11-06
-Post-History: 2017-10-26
+Last-Modified: 2017-11-16
+Post-History: 2017-10-26, 2017-11-16
Content-Type: text/x-rst
Requires: 59, 61
Replaces: 44, 58, 60
@@ -365,6 +365,34 @@ uncompressed content and the specification is free to choose either
of the files using the same base name.
+Combining multiple Manifest trees (informational)
+-------------------------------------------------
+
+This specification permits nesting multiple hierarchical Manifest trees.
+In this layout, the specific directories of the Manifest tree can
+be verified both as a part of another top-level Manifest,
+and as an independent Manifest tree (when obtained without the parent
+directory).
+
+For this to work, the sub-Manifest file in the directory must also
+satisfy the requirements for the top-level Manifest file. That is:
+
+- it must be named ``Manifest`` and not compressed,
+
+- it must cover all the files in this directory and its subdirectories
+ (i.e. no files from the directory tree can be covered by parent
+ Manifest),
+
+- if authenticity verification is desired, it must be OpenPGP-signed.
+
+It should be noted that if such a directory is a subdirectory of a valid
+Manifest tree, the sub-Manifest needs to be valid according
+to the top-level Manifest and the OpenPGP signature is disregarded
+as detailed in `Manifest file locations and nesting`_. The top-level
+behavior is exhibited only when the directory is obtained without parent
+directories.
+
+
An example Manifest file (informational)
----------------------------------------
@@ -792,7 +820,7 @@ for the ``Manifest`` file in every package directory:
- all ``.ebuild`` files need to use the ``EBUILD`` tag,
-` the ``metadata.xml`` and ``ChangeLog`` files need to use
+- the ``metadata.xml`` and ``ChangeLog`` files need to use
the ``MISC`` tag,
- the Manifest can be signed to provide authenticity verification,