From 174758e1ea744545b9c77d5598230253d6ddfc94 Mon Sep 17 00:00:00 2001 From: Karen Arutyunov Date: Wed, 22 Dec 2021 18:36:24 +0300 Subject: Mention '*' marker for requirement alternatives in manual Also swap '?' and '*' in the depends value definition to better match the new dependencies representation syntax. --- doc/manual.cli | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/manual.cli b/doc/manual.cli index 901c4da..ae02f89 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -610,8 +610,8 @@ license: [; ] [build-warning-email]: [; ] [build-error-email]: [; ] -[depends]: [?][*] [; ] -[requires]: [?] [] [; ] +[depends]: [*][?] [; ] +[requires]: [*][?] [] [; ] [tests]: [*] [] [examples]: [*] [] @@ -1033,7 +1033,7 @@ build error notifications are sent to this email. \h2#manifest-package-depends|\c{depends}| \ -[depends]: [?][*] [; ] +[depends]: [*][?] [; ] = [ '|' ]* = [] @@ -1171,7 +1171,7 @@ are treated the same): \h2#manifest-package-requires|\c{requires}| \ -[requires]: [?] [] [; ] +[requires]: [*][?] [] [; ] = [ '|' ]* = | @@ -1181,8 +1181,8 @@ are treated the same): The package requirements (other than other packages). Such requirements are normally checked during package configuration by the build system and the only purpose of capturing them in the manifest is for documentation. Similar to -\c{depends}, a value that starts with \c{?} is a conditional -requirement. For example: +\c{depends}, a value that starts with \c{*} is a build-time requirement and/or +with \c{?} is a conditional requirement. For example: \ requires: linux | windows | macos @@ -1229,7 +1229,7 @@ windows \ gcc[_X.Y.Z] ; For example: gcc_6, gcc_4.9, gcc_5.0.0 clang[_X.Y] ; For example: clang_6, clang_3.4, clang_3.4.1 -msvc[_N.U] ; For example: msvc_14, msvc_15.3 +msvc[_N.U] ; For example: msvc_14, msvc_15.3 \ The following pre-defined ids are recognized by automated build bots: -- cgit v1.1