| 1 |
Rather than limiting the GLEP to list changes from GLEP 44, include |
| 2 |
a short inline explanation of the base Manifest format. This makes |
| 3 |
the standard more standalone, and GLEP 44 did not do a very good job |
| 4 |
of describing the format either. |
| 5 |
|
| 6 |
Signed-off-by: Michał Górny <mgorny@g.o> |
| 7 |
--- |
| 8 |
glep-0074.rst | 6 ++++++ |
| 9 |
1 file changed, 6 insertions(+) |
| 10 |
|
| 11 |
diff --git a/glep-0074.rst b/glep-0074.rst |
| 12 |
index 0117c4b..ff8002f 100644 |
| 13 |
--- a/glep-0074.rst |
| 14 |
+++ b/glep-0074.rst |
| 15 |
@@ -68,6 +68,12 @@ repurposed as a generic *tag* that could also indicate additional |
| 16 |
(non-checksum) metadata. Appropriately, those tags can be followed by |
| 17 |
other space-separated values. |
| 18 |
|
| 19 |
+The Manifest file is a line-oriented text file. Every line comprises |
| 20 |
+a single Manifest entry and consists of one or more fields separated |
| 21 |
+by a single space character (``U+0020``). The tags and their |
| 22 |
+corresponding fields are defined in the `modern Manifest tags`_ |
| 23 |
+and `deprecated Manifest tags`_ sections. |
| 24 |
+ |
| 25 |
Unless specified otherwise, the paths used in the Manifest files |
| 26 |
are relative to the directory containing the Manifest file. The paths |
| 27 |
must not reference the parent directory (``..``). Forward slash (``/``) |
| 28 |
-- |
| 29 |
2.37.3 |
Archives