From 3d8cd06cf98438a3ca4299d0ba77c84c029102a0 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Wed, 11 Jul 2018 10:46:17 +0200
Subject: Specify 'project' package manifest value

---
 doc/manual.cli | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/doc/manual.cli b/doc/manual.cli
index 3f05aa0..ccd1498 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -494,6 +494,7 @@ sections.
 \
 name: <name>
 version: <version>
+[project]: <name>
 [priority]: <priority> [; <comment>]
 summary: <text>
 license: <licenses> [; <comment>]
@@ -541,6 +542,24 @@ format description. Note that the version case is preserved for display, in
 file names, etc.
 
 
+\h2#manifest-package-project|\c{project}|
+
+\
+[project]: <name>
+\
+
+The project this package belongs to. The project name has the same
+restrictions as the package name (see \l{#package-name Package Name} for
+details) and its case is preserved for display, in directory names, etc. If
+unspecified, then the project name is assumed to be the same as the package
+name.
+
+Projects are used to group related packages together in order to help with
+organization and discovery in repositories. For example, packages \c{hello},
+\c{libhello}, and \c{libhello2} could all belong to project \c{hello}. By
+convention, projects of library packages are named without the \c{lib} prefix.
+
+
 \h2#manifest-package-|\c{priority}|
 
 \
-- 
cgit v1.1