From dd591dae0f04035f4c4697cdd0d2c58461cddf06 Mon Sep 17 00:00:00 2001
From: Karen Arutyunov <karen@codesynthesis.com>
Date: Mon, 4 Nov 2019 23:33:28 +0300
Subject: Add support for testing build system modules to worker

---
 doc/manual.cli | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)

(limited to 'doc')

diff --git a/doc/manual.cli b/doc/manual.cli
index 66c2b02..43a2709 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -881,6 +881,39 @@ bpkg -v test <package-name>
 For details on configuring and testing installation refer to
 \l{#arch-controller Controller Logic}.
 
+If the package is a build system module, then it is built and tested (using
+the bundled tests) in a separate configuration that mimics the one used to
+build \c{build2} itself. Note that the configuration and environment options
+and variables are not passed to commands that may affect this configuration.
+Such commands, therefore, have no associated \i{step id}:
+
+\
+#
+#
+b -V create config.import=~host
+bpkg -v create --existing
+
+# bpkg.configure.add
+#
+bpkg -v add <repository-url>
+
+# bpkg.configure.fetch
+#
+bpkg -v fetch --trust <repository-fp>
+
+#
+#
+bpkg -v build --yes --configure-only <package-name>/<package-version>
+
+#
+#
+bpkg -v update <package-name>
+
+# if the test operation is supported by the package:
+#
+bpkg -v test <package-name>
+\
+
 As an example, the following POSIX shell script can be used to setup the
 environment for building C and C++ packages with GCC 9 on most Linux
 distributions.
-- 
cgit v1.1