From 3860ef4ca137e121aa7f7ba1ff5e531d0acfef12 Mon Sep 17 00:00:00 2001
From: Karen Arutyunov <karen@codesynthesis.com>
Date: Mon, 16 Nov 2020 23:38:42 +0300
Subject: Make use of bpkg --all-pattern option in build scripts and
 installation documentation

---
 build.sh.in | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

(limited to 'build.sh.in')

diff --git a/build.sh.in b/build.sh.in
index 613dad3..0c48831 100644
--- a/build.sh.in
+++ b/build.sh.in
@@ -555,18 +555,16 @@ fi
 # Build, install, and verify the build system modules.
 #
 packages=
-package_versions=
 tests=
 
 for m in $module_list; do
-  packages="$packages libbuild2-$m"
-  package_versions="$package_versions libbuild2-$m/$(module_version "$m")"
+  packages="$packages libbuild2-$m/$(module_version "$m")"
   tests="$tests tests/libbuild2-$m-tests/"
 done
 
 if test -n "$packages"; then
-  run bpkg build --for install $package_versions
-  run bpkg install $packages
+  run bpkg build --for install $packages
+  run bpkg install --all-pattern=libbuild2-*
 fi
 
 run cd "$owd"
-- 
cgit v1.1