Re: Simple Instructions/packages for Installing, SBCL/Emacs/Slime ???
"Scott E. Fahlman" <[email protected]> Wed, 23 Apr 2025 16:53:13 -0400
| Newsgroups | gmane.lisp.steel-bank.general |
|---|---|
| Message-ID | <CAMUh8f7yAO2XQXMdXujP1vx-A4_ArhCVixMEpiqcreerGV65Lw@mail.gmail.com> |
Hi Robert, Thanks. This all-inclusive image might be the lowest-hassle delivery vehicle for end users. But it sounds like it would require a lot of work to set up, and the result would be a brittle core image that has to be rebuilt by someone every time there's an update in any component or in the environment (a new MacOS version, for example) changes. And it would be inflexible, requiring a complete new build if someone needs a different set of components or settings. So that could be great if someone wants to do that work and commit to maintaining that. But finding that volunteer might not be easy. Cheers, Scott On Wed, Apr 23, 2025 at 4:37 PM Robert Goldman <[email protected]> wrote: > This might be the sort of thing that is best handled by making a docker > image. > > One could make a docker image for SBCL that works on either AMD64 or > ARM64, covering Windows and Mac. I have done this myself based on the > images that used to be provided by the CL Foundation. See the images > rpgoldman/sbcl:latest (I use these for testing CL systems). > > One could further build from this initial docker image a new one that > contains also Emacs with SLIME (or SLY) pre-installed. > > That would be easier in some ways. It would still have a couple of > problems: > > 1. > > It would probably be a nuisance to run Emacs inside the container. > From outside the container, one could run Emacs with SLIME using the SBCL > inside the kernel. It might take some work to get this to work properly, > and then the user would still have to install emacs + slime. > 2. > > One would have to run the container with the user's directory of Lisp > code mounted into the docker. That could be automated by a shell script > (bat) file that would start up the container (and start a swank or slynk > server). > 3. > > Another subtlety: one would probably want to also mount the quicklisp > directory into the container, too, so that it wouldn't have to be > regenerated every time one started up the image. > > There would still be a fair amount of work getting this to work. > _______________________________________________ Sbcl-help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sbcl-help