From 70a600e1b5d29fdff1a1f80d875fb2eed51afde4 Mon Sep 17 00:00:00 2001 From: Matthew Flatt Date: Sun, 27 Dec 2020 19:08:19 -0700 Subject: [PATCH] build-instruction typos and clarifications --- build.md | 7 ++++--- pkgs/racket-build-guide/distribute.scrbl | 6 ++++-- racket/src/README.txt | 3 +-- 3 files changed, 9 insertions(+), 7 deletions(-) diff --git a/build.md b/build.md index 39b8c562e8..0c02ba02fe 100644 --- a/build.md +++ b/build.md @@ -368,8 +368,8 @@ repository’s top-level makefile and the `"distro-build"` package. The `installers` target of the makefile will do everything to generate installers: build a server on the current machine, run clients on hosts -specified via `CONFIG`, and start/stop VirtualBox virtual machines that -act as client machines. +specified via `CONFIG`, and start/stop VirtualBox virtual machines or +Docker containers that act as client machines. If the server is already built, the `installers-from-built` target will drive the client builds without re-building the server. @@ -392,7 +392,8 @@ build (not the one for building installers), you can use   `make describe-clients CONFIG=my-site-config.rkt` to see, without building anything, the effect of the configuration in -`"my-site-config.rkt"` and the planned build steps. +`"my-site-config.rkt"` and the planned build steps. See also the +`#:fake-installers?` site-configuration option. The default `CONFIG` path is `"build/site.rkt"`, so you could put your configuration file there and omit the `CONFIG` argument to `make`. A diff --git a/pkgs/racket-build-guide/distribute.scrbl b/pkgs/racket-build-guide/distribute.scrbl index 8f375c1359..1feb09a81e 100644 --- a/pkgs/racket-build-guide/distribute.scrbl +++ b/pkgs/racket-build-guide/distribute.scrbl @@ -36,7 +36,8 @@ Git repository's top-level makefile and @|distro-build-package|. The @exec{installers} target of the makefile will do everything to generate installers: build a server on the current machine, run clients on hosts specified via @exec{CONFIG}, and start/stop -VirtualBox virtual machines that act as client machines. +VirtualBox virtual machines or Docker containers that act as client +machines. If the server is already built, the @exec{installers-from-built} target will drive the client builds without re-building the server. @@ -59,7 +60,8 @@ some Racket build (not the one for building installers), you can use @commandline{make describe-clients CONFIG=my-site-config.rkt} to see, without building anything, the effect of the configuration in -@filepath{my-site-config.rkt} and the planned build steps. +@filepath{my-site-config.rkt} and the planned build steps. See also the +@racket[#:fake-installers?] site-configuration option. The default @exec{CONFIG} path is @filepath{build/site.rkt}, so you could put your configuration file there and omit the @exec{CONFIG} diff --git a/racket/src/README.txt b/racket/src/README.txt index 2872fdd4da..facf71d110 100644 --- a/racket/src/README.txt +++ b/racket/src/README.txt @@ -72,7 +72,6 @@ If you need more information specific to Racket BC, see "bc/README.txt". - ======================================================================== Compiling for supported Unix variants (including Linux) ======================================================================== @@ -458,7 +457,7 @@ See also the shared sources below, which includes rktio, the macro expander, and schemify. Sources for the Racket BC implementation -------------------------------------------------- +---------------------------------------- * "bc" --- `racket` BC executable