qlot VS roswell

Other options are:

- Quicklisp -really slick, libraries in there are curated. (with https support here: https://github.com/rudolfochrist/ql-https and here: https://github.com/snmsts/quicklisp-https.git)

- for project-local dependencies like virtualenv: https://github.com/fukamachi/qlot

- a new, more traditional one: https://www.clpm.dev (CLPM comes as a pre-built binary, supports HTTPS by default, supports installing multiple package versions, supports versioned systems, and more)

For recent Quicklisp upgrades: http://ultralisp.org/

Ocicl is very new (5 days) and tries a new approach, building "on tools from the world of containers".

I frequently use roswell (and occasionally qlot) to manage my CL distributions and packages. Native support for roswell would be fantastic!

An easy example would be to look at qlot.asd.

I think definitely some kind of integration with quicklisp and/or qlot would be amazing, so you can open a project and have all the dependencies pulled and ready for your project.

I prefer to use Qlot.

BTW, Roswell makes it easier to run scripts: https://github.com/roswell/roswell/wiki/Roswell-as-a-Scripti...

It is also a tool to install various CL implementations, and to install software.

It doesn't come with a choice of built-in libraries.

The Github wiki: https://github.com/roswell/roswell/wiki

download failed "https://github.com/roswell/roswell/releases/download/21.10.14.111/roswell_21.10.14.111_amd64.zip" 404 "Not Found"

You could also be a roswell user, in which case your project might have a roswell directory. Again, you can look at the qlot project for reference.

Clack is a web application environment for Common Lisp inspired by Python's WSGI and Ruby's Rack. Clack provides a script to start a web server. It's useful when you deploy to production environment. You need to install Roswell before as Clack depends on it.

Common Lisp itself has Roswell, which I am disappointed to see is not even mentioned in the article.

https://github.com/roswell/roswell

w.r.t to image size, ScriptL takes care of that since everything is in the same image. You could also use something like buildapp or cl-launch to make a multi-call binary that you compile your scripts into. I think I recall roswell allowing multiple entry points too, but I never could get it to work. Possibly PEBKAC on my end.