aboutsummaryrefslogtreecommitdiff
path: root/UPGRADE.cli
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2018-12-07 14:15:19 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2018-12-07 14:15:19 +0200
commit39ea3597690e1ece9e0d1f23e8ff200674e2a406 (patch)
treed31ee2999e2d6801e9ed9092d0d3b08cf02500e5 /UPGRADE.cli
parent80d52a6d4e5cfd157cc3188996ff5b567d7d4dad (diff)
Minor install/upgrade documentation improvements
Diffstat (limited to 'UPGRADE.cli')
-rw-r--r--UPGRADE.cli12
1 files changed, 9 insertions, 3 deletions
diff --git a/UPGRADE.cli b/UPGRADE.cli
index 964749c..baa00fa 100644
--- a/UPGRADE.cli
+++ b/UPGRADE.cli
@@ -28,9 +28,15 @@ We recommend that you use a dirty upgrade for patch releases with the same
\c{X.Y} (\c{MAJOR.MINOR}) version and a staged upgrade otherwise. With patch
releases we guarantee not to alter the installation file set.
-\N|Note that without periodic upgrades your version of the toolchain may
-become too old to be able to upgrade itself. In this case you will have to
-fall back onto the bootstrap process.|
+\N|Without periodic upgrades your version of the toolchain may become too old
+to be able to upgrade itself. In this case you will have to fall back onto the
+bootstrap process.|
+
+\N|The below upgrade process does not cover upgrading the \c{baseutils} and
+\c{mingw} packages on Windows (see \l{#bootstrap-windows Bootstrapping on
+Windows} for details). We recommend using the bootstrap process to upgrade
+these packages since all the straightforward upgrade sequences would lead to
+either the old toolchain using the new utilities or vice versa.|
The dirty upgrade is straightforward: