aboutsummaryrefslogtreecommitdiff
path: root/src/propspec.lisp
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2021-12-10 14:38:59 -0700
committerSean Whitton <spwhitton@spwhitton.name>2021-12-13 15:32:31 -0700
commitb819c80ed5ee2492924bf86beea06abd78dc0cbc (patch)
treee022d0cbaf2089f4806ab2ec006eeed007652fe0 /src/propspec.lisp
parentb6283709c3813c6b1e357a073880b2a9ceb2e703 (diff)
downloadconsfigurator-b819c80ed5ee2492924bf86beea06abd78dc0cbc.tar.gz
IN-CONSFIG: don't accept NIL as argument
If *CONSFIG* is NIL because the user called (in-consfig nil), then initialising a propspec without any supplied list of ASDF systems will still result in a NO-CONSFIG warning, the text of which suggests calling IN-CONSFIG. For now, avoid that situation by disallowing (in-consfig nil). If the user doesn't want to use the *CONSFIG* feature, it is probably best if they muffle the warning or explicitly supply a list of ASDF systems in each piece of code that initialises propspecs, rather than declaring (in-consfig nil). Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'src/propspec.lisp')
-rw-r--r--src/propspec.lisp2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/propspec.lisp b/src/propspec.lisp
index 2ef61d2..57209fc 100644
--- a/src/propspec.lisp
+++ b/src/propspec.lisp
@@ -122,6 +122,8 @@ property combinators you intend to use in specifying propspecs.
Consfigurator uses this information when starting up remote Lisp images to
effect deployments: it sends over the ASDF systems specified by SYSTEMS."
+ (when (null systems)
+ (simple-program-error "Cannot pass NIL to IN-CONSFIG."))
(setq systems (ensure-cons systems))
(let ((sym (intern "*CONSFIG*")))
`(eval-when (:compile-toplevel :load-toplevel :execute)