path: root/BOOTSTRAP-UNIX.cli
diff options
authorBoris Kolpackov <boris@codesynthesis.com>2017-05-08 15:42:10 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2017-05-08 15:42:10 +0200
commita38d1d18cf033fcdd4c9b52ad106a79ae6fb2791 (patch)
tree33e49527306ba5daf142ba7e3acea45c6cc410ee /BOOTSTRAP-UNIX.cli
parentc590daff1bfc968a99bc95a4cf4847b5e4b8fc02 (diff)
Add several clarifications to bootstrap instructions
Diffstat (limited to 'BOOTSTRAP-UNIX.cli')
1 files changed, 5 insertions, 1 deletions
diff --git a/BOOTSTRAP-UNIX.cli b/BOOTSTRAP-UNIX.cli
index 9923316..5879a33 100644
@@ -83,7 +83,7 @@ $ ./build.sh --install-dir /opt/build2 --sudo sudo clang++
Note also that at about half way through (\c{bpkg fetch} at step 4 below) the
script will stop and prompt you to verify the authenticity of the repository
certificate. To run the script unattended you can specify the certificate
-fingerprint with the \c{--trust} option.
+fingerprint with the \c{--trust} option (see \c{build.sh -h} for details).
The end result of the bootstrap process (performed either with the script or
manually) is the installed toolchain as well as the \c{bpkg} configuration in
@@ -95,6 +95,10 @@ $ cd build2-toolchain-X.Y
$ bpkg uninstall build2 bpkg
+Note also that in both cases (manual or scripted bootstrap), if something
+goes wrong and you need to restart the process, you \b{must} start with a
+clean toolchain source by unpacking it afresh from the archive.
The rest of this section outlines the manual bootstrap process.