Gentoo Archives: gentoo-commits

From: "Michał Górny" <mgorny@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] data/glep:glep-manifest commit in: /
Date: Mon, 20 Nov 2017 17:26:26
Message-Id: 1510827422.09ed01f5a480b0b8042bddc93ef19a02e02326d0.mgorny@gentoo
1 commit: 09ed01f5a480b0b8042bddc93ef19a02e02326d0
2 Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
3 AuthorDate: Mon Nov 13 17:06:27 2017 +0000
4 Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
5 CommitDate: Thu Nov 16 10:17:02 2017 +0000
6 URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=09ed01f5
7
8 glep-0074: Explain combining multiple Manifest trees
9
10 The idea has been originally suggested by Robin H. Johnson.
11
12 glep-0074.rst | 34 +++++++++++++++++++++++++++++++---
13 1 file changed, 31 insertions(+), 3 deletions(-)
14
15 diff --git a/glep-0074.rst b/glep-0074.rst
16 index e8fc849..42c0c9e 100644
17 --- a/glep-0074.rst
18 +++ b/glep-0074.rst
19 @@ -8,8 +8,8 @@ Type: Standards Track
20 Status: Draft
21 Version: 1
22 Created: 2017-10-21
23 -Last-Modified: 2017-11-06
24 -Post-History: 2017-10-26
25 +Last-Modified: 2017-11-16
26 +Post-History: 2017-10-26, 2017-11-16
27 Content-Type: text/x-rst
28 Requires: 59, 61
29 Replaces: 44, 58, 60
30 @@ -365,6 +365,34 @@ uncompressed content and the specification is free to choose either
31 of the files using the same base name.
32
33
34 +Combining multiple Manifest trees (informational)
35 +-------------------------------------------------
36 +
37 +This specification permits nesting multiple hierarchical Manifest trees.
38 +In this layout, the specific directories of the Manifest tree can
39 +be verified both as a part of another top-level Manifest,
40 +and as an independent Manifest tree (when obtained without the parent
41 +directory).
42 +
43 +For this to work, the sub-Manifest file in the directory must also
44 +satisfy the requirements for the top-level Manifest file. That is:
45 +
46 +- it must be named ``Manifest`` and not compressed,
47 +
48 +- it must cover all the files in this directory and its subdirectories
49 + (i.e. no files from the directory tree can be covered by parent
50 + Manifest),
51 +
52 +- if authenticity verification is desired, it must be OpenPGP-signed.
53 +
54 +It should be noted that if such a directory is a subdirectory of a valid
55 +Manifest tree, the sub-Manifest needs to be valid according
56 +to the top-level Manifest and the OpenPGP signature is disregarded
57 +as detailed in `Manifest file locations and nesting`_. The top-level
58 +behavior is exhibited only when the directory is obtained without parent
59 +directories.
60 +
61 +
62 An example Manifest file (informational)
63 ----------------------------------------
64
65 @@ -792,7 +820,7 @@ for the ``Manifest`` file in every package directory:
66
67 - all ``.ebuild`` files need to use the ``EBUILD`` tag,
68
69 -` the ``metadata.xml`` and ``ChangeLog`` files need to use
70 +- the ``metadata.xml`` and ``ChangeLog`` files need to use
71 the ``MISC`` tag,
72
73 - the Manifest can be signed to provide authenticity verification,