From bd1d90d876c07dbbfac74f6a2b55d879843fc9cc Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Mon, 22 Mar 2021 08:56:43 -0700 Subject: 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 --- src/data/asdf.lisp | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) (limited to 'src/data') diff --git a/src/data/asdf.lisp b/src/data/asdf.lisp index 2d61c49..51ac344 100644 --- a/src/data/asdf.lisp +++ b/src/data/asdf.lisp @@ -21,14 +21,13 @@ ;; could we have both :asdf-monolithic and :asdf-something_else where in the ;; latter we filter out the names of systems already known to be available on ;; the remote side, so those don't need to be uploaded? for example, the -;; :debian-sbcl connection type can try to install them with apt on the remote -;; side, then ask asdf for a concatenated source for everything excluding -;; those. if asdf can't be asked to do that, maybe we can ask it to produce -;; one file per system, and then we eliminate those we don't want and -;; concatenate the result ourselves. maybe we can create a fake system object -;; based on the real one, remove some deps from it according to a known -;; mapping of systems to Debian package names, then ask asdf to concatenate -;; that system +;; :sbcl connection type can try to install them with apt on the remote side, +;; then ask asdf for a concatenated source for everything excluding those. if +;; asdf can't be asked to do that, maybe we can ask it to produce one file per +;; system, and then we eliminate those we don't want and concatenate the +;; result ourselves. maybe we can create a fake system object based on the +;; real one, remove some deps from it according to a known mapping of systems +;; to Debian package names, then ask asdf to concatenate that system (defmethod register-data-source ((type (eql :asdf)) &key) (cons #'asdf-data-source-check #'get-path-to-concatenated-system)) -- cgit v1.2.3