diff options
| author | Sean Whitton <spwhitton@spwhitton.name> | 2021-03-22 08:56:43 -0700 |
|---|---|---|
| committer | Sean Whitton <spwhitton@spwhitton.name> | 2021-03-22 08:59:18 -0700 |
| commit | bd1d90d876c07dbbfac74f6a2b55d879843fc9cc (patch) | |
| tree | 6d97e3f8bdf317df885d1b7b50edaed156bab38e /doc/connections.rst | |
| parent | 29b58a026814277d0bdbaaa7f3bc101710111b85 (diff) | |
| download | consfigurator-bd1d90d876c07dbbfac74f6a2b55d879843fc9cc.tar.gz | |
rename :DEBIAN-SBCL -> :SBCL & use a property to install sbcl
Unconditionally calling apt was actually the only Debian-specific thing about
the connection type.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'doc/connections.rst')
| -rw-r--r-- | doc/connections.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/connections.rst b/doc/connections.rst index e14aa82..7e81826 100644 --- a/doc/connections.rst +++ b/doc/connections.rst @@ -58,11 +58,11 @@ use the ``chroot(2)`` system call anyway). More generally, you should avoid using this connection type within a Lisp image which might try to execute other deployments in parallel. Typical usage would be something like:: - (deploy (:sudo :debian-sbcl (:chroot.fork :into "...")) ...) + (deploy (:sudo :sbcl (:chroot.fork :into "...")) ...) In some situations you might want to have a connection chain which effectively -uses a connection type like ``:DEBIAN-SBCL`` twice in a row, so that the first -Lisp image can execute deployments in parallel while the second forks into the +uses a connection type like ``:SBCL`` twice in a row, so that the first Lisp +image can execute deployments in parallel while the second forks into the chroot (typically by having a ``DEPLOYS`` property with connection type -``:DEBIAN-SBCL`` as one of the properties applied by a deployment whose -connection chain itself ends with ``:DEBIAN-SBCL``). +``:SBCL`` as one of the properties applied by a deployment whose connection +chain itself ends with ``:SBCL``). |