aboutsummaryrefslogtreecommitdiff
path: root/bpkg/build-options.cli
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2015-11-25 09:19:19 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2015-11-25 09:19:19 +0200
commit87e476cf192b70c133a1bf00efa8586348326092 (patch)
tree88d70237857ceec7416c8edd7a3d8cf2d8093fb5 /bpkg/build-options.cli
parentb244bc6ef9d36d651c40de818ef33246919fc859 (diff)
New command line help setup
Diffstat (limited to 'bpkg/build-options.cli')
-rw-r--r--bpkg/build-options.cli51
1 files changed, 26 insertions, 25 deletions
diff --git a/bpkg/build-options.cli b/bpkg/build-options.cli
index 7164dbb..00a4c9c 100644
--- a/bpkg/build-options.cli
+++ b/bpkg/build-options.cli
@@ -8,41 +8,42 @@ include <bpkg/configuration-options.cli>;
"\name=bpkg-build"
"\summary=build one or more packages"
+namespace bpkg
{
-"<options> <pkg> <ver> <file> <dir>",
-
-"\h|SYNOPSIS|
+ {
+ "<options> <pkg> <ver> <file> <dir>",
-\c{\b{bpkg build} [<options>] (<pkg>[/<ver>] | <file> | <dir>)...}
+ "\h|SYNOPSIS|
-\h|DESCRIPTION|
+ \c{\b{bpkg build} [<options>] (<pkg>[/<ver>] | <file> | <dir>)...}
-The \cb{build} command builds one or more packages including all their
-prerequisites. Each package can be specified as just the name (<pkg>) with
-optional package version (<ver>) in which case the package will be
-automatically fetched from one of the configuration's source repositories
-(see the \cb{rep-add} and \cb{rep-fetch} commands). Alternatively, the
-package can be specified as either the path to the package source archive
-(<file>) or package source directory (<dir>). See the \cb{pkg-fetch} and
-\cb{pkg-unpack} commands for more information on the semantics of specifying
-the package as an archive or directory.
+ \h|DESCRIPTION|
-Packages that are specified explicitly on the command line will be \i{held},
-that is, they will not be considered for automatic removal if they no longer
-have any dependents. Packages that are specified with the explicit package
-version (<ver>) or as an archive or directory, will, in addition, have their
-versions held, that is, they will not be automatically upgraded.
+ The \cb{build} command builds one or more packages including all their
+ prerequisites. Each package can be specified as just the name (<pkg>) with
+ optional package version (<ver>) in which case the package will be
+ automatically fetched from one of the configuration's source repositories
+ (see the \cb{rep-add} and \cb{rep-fetch} commands). Alternatively, the
+ package can be specified as either the path to the package source archive
+ (<file>) or package source directory (<dir>). See the \cb{pkg-fetch} and
+ \cb{pkg-unpack} commands for more information on the semantics of
+ specifying the package as an archive or directory.
-The \cb{build} command also supports several \cb{--*-only} options that allow
-you to limit the amount of work that will be done.
+ Packages that are specified explicitly on the command line will be
+ \i{held}, that is, they will not be considered for automatic removal if
+ they no longer have any dependents. Packages that are specified with the
+ explicit package version (<ver>) or as an archive or directory, will, in
+ addition, have their versions held, that is, they will not be
+ automatically upgraded.
-\h|OPTIONS|"
-}
+ The \cb{build} command also supports several \cb{--*-only} options that
+ allow you to limit the amount of work that will be done."
+ }
-namespace bpkg
-{
class build_options: configuration_options
{
+ "\h|BUILD OPTIONS|"
+
bool --yes|-y
{
"Assume the answer to all prompts is \cb{yes}."