From 5d513688ae07d96910dd1eef83bdad4e9d780373 Mon Sep 17 00:00:00 2001
From: Karen Arutyunov <karen@codesynthesis.com>
Date: Thu, 22 Apr 2021 21:57:13 +0300
Subject: Add support for linked configurations

---
 bpkg/pkg-status.cli | 20 ++++++++++++++++----
 1 file changed, 16 insertions(+), 4 deletions(-)

(limited to 'bpkg/pkg-status.cli')

diff --git a/bpkg/pkg-status.cli b/bpkg/pkg-status.cli
index 24e1dc8..d45c4ae 100644
--- a/bpkg/pkg-status.cli
+++ b/bpkg/pkg-status.cli
@@ -32,10 +32,12 @@ namespace bpkg
      \cb{stderr}.
 
      The status output format is regular with components separated with
-     spaces. Each line starts with the package name (and version, if
-     specified) followed by one of the status words listed below.  Some of
-     them can be optionally followed by '\cb{,}' (no spaces) and a sub-status
-     word.
+     spaces. Each line starts with the package name and version (if specified)
+     followed by one of the status words listed below. Some of them can be
+     optionally followed by '\cb{,}' (no spaces) and a sub-status word. Lines
+     corresponding to dependencies from linked configurations will
+     additionally mention the configuration directory in square brackets after
+     the package name and version.
 
      \dl|
 
@@ -146,6 +148,16 @@ namespace bpkg
      !libfoo configured,system * available 1.1.0 1.1.1
      \
 
+     Another example of the status output this time including dependencies:
+
+     \
+     bpkg status -r libbaz
+     !libbaz configured 1.0.0
+       libfoo configured 1.0.0
+         bison [.bpkg/host/] configured 1.0.0
+       libbar configured 2.0.0
+     \
+
      "
   }
 
-- 
cgit v1.1