Initial naming adjustments (bdep)

4 files changed, 18 insertions, 18 deletions

diff --git a/INSTALL b/INSTALL
index 5539259..4355123 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,5 +1,5 @@
-Unless you specifically only need the build2 package manager and not the
-complete build2 toolchain, you should use the build2-toolchain distribution
+Unless you specifically only need the build2 package dependency manager and not
+the complete build2 toolchain, you should use the build2-toolchain distribution
 instead.
 
 If you do want just the package manager, then you can build it using the
diff --git a/README b/README
index 21abe33..206f156 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-This package contains the build2 package manager.
+This package contains the build2 package dependency manager.
 
 build2 is an open source, cross-platform toolchain for building and packaging
 C++ code. Its aim is a modern build system and package manager for the C++
diff --git a/bpkg/bpkg.cli b/bpkg/bpkg.cli
index c1109d0..bd4b996 100644
--- a/bpkg/bpkg.cli
+++ b/bpkg/bpkg.cli
@@ -6,7 +6,7 @@ include <bpkg/common.cli>;
 
 "\section=1"
 "\name=bpkg"
-"\summary=package manager"
+"\summary=package dependency manager"
 
 namespace bpkg
 {
@@ -22,9 +22,9 @@ namespace bpkg
 
      \h|DESCRIPTION|
 
-     The \cb{build2} package manager is used to manipulate configurations,
-     packages, and repositories using a set of commands that are summarized
-     below.
+     The \cb{build2} package dependency manager is used to manipulate build
+     configurations, packages, and repositories using a set of commands that
+     are summarized below.
 
      For a detailed description of any command or help topic, use the
      \cb{help} command or see the corresponding man page (the man pages have
@@ -40,15 +40,15 @@ namespace bpkg
     "",
     "",
 
-    "A \i{bpkg configuration} is a directory that will contain packages built
-     with similar settings. For example, a configuration can be for a specific
-     target (\cb{i686}, \cb{x86_64}), compiler (\cb{clang}, \cb{gcc}) compile
-     options (\cb{-O3}, \cb{-g}), and so on. Configurations are relatively
-     cheap and can be created and thrown away as needed. Configurations can be
-     moved and copied by simply moving and copying the directories. Note,
-     however, that a move or copy may render some packages out-of-date. In the
-     \cb{build2} build system terms a \cb{bpkg} configuration is an
-     amalgamation that contains packages as subprojects.
+    "A \cb{bpkg} \i{build configuration} is a directory that will contain
+     packages built with similar settings. For example, a configuration can be
+     for a specific target (\cb{i686}, \cb{x86_64}), compiler (\cb{clang},
+     \cb{gcc}) compile options (\cb{-O3}, \cb{-g}), and so on. Configurations
+     are relatively cheap and can be created and thrown away as needed.
+     Configurations can be moved and copied by simply moving and copying the
+     directories. Note, however, that a move or copy may render some packages
+     out-of-date. In the \cb{build2} build system terms a \cb{bpkg} build
+     configuration is an amalgamation that contains packages as subprojects.
 
      A \i{bpkg package} is an archive or directory that contains a \cb{build2}
      project plus the package \cb{manifest} file. \cb{bpkg} can either use
diff --git a/manifest b/manifest
index 4be11de..6a0870c 100644
--- a/manifest
+++ b/manifest
@@ -1,9 +1,9 @@
 : 1
 name: bpkg
 version: 0.7.0-a.0.z
-summary: build2 package manager
+summary: build2 package dependency manager
 license: MIT
-tags: build2, c++, package, manager
+tags: build2, c++, package, dependency, manager
 description-file: README
 changes-file: NEWS
 url: https://build2.org