From 09b1d3ff6e0d0db3210207b94c6106ea647e9318 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Mon, 6 Sep 2021 08:28:53 +0200
Subject: Add argument grouping support for dependencies in bdep-{sync,init}

---
 bdep/sync.cli | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

(limited to 'bdep/sync.cli')

diff --git a/bdep/sync.cli b/bdep/sync.cli
index fcc1417..c25cd7d 100644
--- a/bdep/sync.cli
+++ b/bdep/sync.cli
@@ -67,6 +67,13 @@ namespace bdep
      Note also that \c{\b{--immediate}|\b{-i}} or \c{\b{--recursive}|\b{-r}}
      can only be specified with an explicit \cb{--upgrade} or \cb{--patch}.
 
+     Configuration variables can be specified to only apply to specific
+     packages in <pkg-args> and <dep-spec> using the argument grouping
+     mechanism (\l{bdep-argument-grouping(1)}). Additionally, packages in
+     <pkg-args> can be placed into specific linked configurations by
+     specifying the configuration with one of the \cb{--config*} options
+     (or \cb{@} notation) using the same grouping mechanism.
+
      If during synchronization a build-time dependency is encountered and
      there is no build configuration of a suitable type associated with the
      project, then the user is prompted (unless the respective
@@ -241,6 +248,18 @@ namespace bdep
     uint16_t --hook = 0;
   };
 
+  // Options that can be specified in a group for ?<pkg> in pkg-args.
+  //
+  class cmd_sync_pkg_options
+  {
+    // Note that this is also used as storage for configuration names
+    // specified as @<name>.
+    //
+    vector<string> --config-name|-n;
+    vector<uint64_t> --config-id;
+    vector<dir_path> --config|-c;
+  };
+
   "
    \h|DEFAULT OPTIONS FILES|
 
-- 
cgit v1.1