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 /src/connection/sudo.lisp | |
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 'src/connection/sudo.lisp')
-rw-r--r-- | src/connection/sudo.lisp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/connection/sudo.lisp b/src/connection/sudo.lisp index 3c7c633..5e2dbf9 100644 --- a/src/connection/sudo.lisp +++ b/src/connection/sudo.lisp @@ -34,8 +34,8 @@ ;; passwords needed for establishing the remaining hops. Depending on how the ;; connection type feeds instructions to the remote Lisp image, this may ;; involve writing your sudo password to a file under ~/.cache on the machine -;; which runs the remote Lisp image. At least :debian-sbcl avoids this by -;; sending your password in on stdin. +;; which runs the remote Lisp image. At least :sbcl avoids this by sending +;; your password in on stdin. ;; TODO Let's require the user pass :PASSWD or :NOPASSWD to indicate whether ;; we'll query prerequisite data sources and always try to send a password on |