oras VS ultralisp

Interesting, I'd not known of this RFC before.

Another example of a content-addressed data store could be OCI registries (more commonly known as container image registries). Using them to store arbitrary artefacts is quite well supported now: https://oras.land/

See https://oras.land/

> ... but still only supports one niche operating system.

1. Linux is not a niche in the target market for this project.

2. The project is written in Common Lisp with hard dependencies on SBCL-provided libraries[1], so there's reason to suspect it should work on other OSes supported by SBCL.

3. Sure, the presence of Makefile and sb-posix imply it requires a POSIX compliant OS, but Linux is not the only one that fits the bill.

4. The included Linux-only binary 'oras' is clearly a vendored artifact, not part of this project, and clearly an OCI client. A simple search shows it is indeed cross-platform[2].

Perhaps you should try what almost every Linux user has had to do when encountering software actually built for only one "niche" operating system that they want to use on their OS: look.

1. https://github.com/ocicl/ocicl/blob/170aff0/ocicl.asd#L34

2. https://github.com/oras-project/oras/releases

oras isn't that unpopular, Helm is using it as an SDK for example. Here are other projects who are using it. https://github.com/oras-project/oras/network/dependents

If it reduces your pain, you can add it to https://ultralisp.org without any hussle.

- as a dockerized daemon (here is my Dockerfile describing a few microservices: https://github.com/ultralisp/ultralisp/blob/master/Dockerfile)

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'm the author and I'm using Emacs + SLY. Happily switched to Emacs from VIM about 10 years ago when decided to invest all my free time into Common Lisp.

And yes, I have real project experience – a lot of Commmon Lisp libraries at https://github.com/40ants and also I'm developing a hosting for CL library distributions: https://ultralisp.org

So far openapi-generator is mostly tested on linux/sbcl and it should work for most spec files. It would be great to have some criticism/feedback/improvement ideas. You can download it from Ultralisp via (ql:quickload :openapi-generator)(you may need to update first (ql:update-dist "ultralisp"))

See also Ultralisp, a Quicklisp distribution that builds every 5 minutes: https://ultralisp.org/ where you can publish packages.

There is also a repository behind Ultralisp.org: https://github.com/ultralisp/ultralisp

Quicklisp ships releases once a month, so it is very possible it didn't pick the latest release yet.

Your solution is to clone the repository into ~/quicklisp/local-projects/.

Another one would be to use the Ultralisp distribution, that ships every five minutes. https://ultralisp.org/

(ql-dist:install-dist "http://dist.ultralisp.org/"