diff options
| author | Karen Arutyunov <karen@codesynthesis.com> | 2022-12-06 22:30:13 +0300 |
|---|---|---|
| committer | Karen Arutyunov <karen@codesynthesis.com> | 2022-12-07 13:40:22 +0300 |
| commit | a91334e64fee910190173f39b6048729db009e4e (patch) | |
| tree | 7fc3e78467dd4f0c983b88c715592f87d1ef55d8 | |
| parent | b7cf0311bf11d0df4524cf86c2a759e27a1f69a7 (diff) | |
Document *-build-config override
| -rw-r--r-- | doc/manual.cli | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/manual.cli b/doc/manual.cli index 53dcb28..9529dac 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -360,8 +360,17 @@ being applied. Currently, only the following value groups can be overridden: build-email build-{warning,error}-email builds build-{include,exclude} *-builds *-build-{include,exclude} +*-build-config \ +For the package configuration-specific build constraint overrides the +corresponding configuration must exist in the package manifest. In contrast, +the package configuration override (\cb{*-build-config}) adds a new +configuration if it doesn't exist and updates the arguments of the existing +configuration otherwise. In the former case, all the potential build +constraint overrides for such a newly added configuration must follow the +corresponding \cb{*-build-config} override. + Note that the build constraints group values (both common and build package configuration-specific) are overridden hierarchically so that the \c{[\b{*-}]\b{build-}{\b{include},\b{exclude}\}} overrides don't affect the |