From f572561f37badb1413c0ba80c1c397be3bf3b15e Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Sat, 21 Jul 2018 12:52:25 +0200 Subject: Specify binary manifest representation --- doc/manual.cli | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/doc/manual.cli b/doc/manual.cli index e760cd9..d6bdf29 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -249,7 +249,7 @@ of a repository, respectively. \h#manifest-format|Manifest Format| -The manifest file is a UTF-8 encoded text file containing a list of name-value +The manifest format is a UTF-8 encoded text containing a list of name-value pairs in the form: \ @@ -487,6 +487,20 @@ license: [; ] In the above example \c{name} is required, \c{license} has an optional component (comment), and \c{description} is optional. +In certain situations (for example, shell scripts) it can be easier to parse +the binary manifest representation. The binary representation does not include +comments and consists of a sequence of name-value pairs in the following form: + +\ +:\0 +\ + +That is, the name and the value are separated by a colon and each pair +(including the last) is terminated with the \c{NUL} character. Note that there +can be no leading or trailing whitespace characters around the name and any +whitespaces after the colon and before the \c{NUL} terminator are part of the +value. + \h#manifest-package|Package Manifest| -- cgit