aboutsummaryrefslogtreecommitdiff
path: root/UPGRADE.cli
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2018-12-05 12:09:05 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2018-12-05 12:09:05 +0200
commit5b18d0d73980102aadc91678b1454b624cf6b253 (patch)
treee3a4402c0a16f57d3217184d076689f3fa374ee6 /UPGRADE.cli
parent216594b08e6d7e1bfa24aab957ee5164ac5eb1c5 (diff)
Update upgrade instructions
Diffstat (limited to 'UPGRADE.cli')
-rw-r--r--UPGRADE.cli8
1 files changed, 6 insertions, 2 deletions
diff --git a/UPGRADE.cli b/UPGRADE.cli
index 92f46ef..964749c 100644
--- a/UPGRADE.cli
+++ b/UPGRADE.cli
@@ -37,10 +37,14 @@ The dirty upgrade is straightforward:
\
$ cd build2-toolchain-X.Y
$ bpkg fetch
-$ bpkg build --for install build2 bpkg bdep
+$ bpkg build --for install -ur build2 bpkg bdep
$ bpkg install build2 bpkg bdep
\
+\N|The \c{-ur} options stands for \c{--upgrade} and \c{--recursive} \- upgrade
+the listed packages and their dependencies, recursively. See
+\l{bpkg-pkg-build(1)} for details.|
+
You may also want to issue the \c{status} command after \c{fetch} to examine
which versions are available. By default \c{bpkg} will upgrade to the latest
available but you can override this by specifying the desired version
@@ -102,7 +106,7 @@ configuration and install the new toolchain with the \c{-stage} suffix:
\
$ cd build2-toolchain-X.Z
-$ bpkg build --for install build2 bpkg bdep
+$ bpkg build --for install -ur build2 bpkg bdep
$ bpkg install \
config.bin.suffix=-stage \
config.install.data_root=root/stage \