qlot
ocicl
| qlot | ocicl | |
|---|---|---|
| 9 | 4 | |
| 384 | 105 | |
| - | 4.8% | |
| 9.7 | 7.9 | |
| 1 day ago | 9 days ago | |
| Common Lisp | Common Lisp | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
qlot
- qlot – a project-local library installer for Common Lisp
- Qlot: Common Lisp Library Manager
-
Ocicl – An ASDF system distribution and management tool for Common Lisp
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".
-
SLT Ide - which implementation to target?
I frequently use roswell (and occasionally qlot) to manage my CL distributions and packages. Native support for roswell would be fantastic!
-
Project and EDE: A potential way to organize project types?
An easy example would be to look at qlot.asd.
-
What features should a Lisp IDE have?
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.
- Is it okay to not specify version of dependencies?
- Qlot v1.0.0 officially released - a project-local library installer for Common Lisp
-
How to load a system outside quicklisp?
I prefer to use Qlot.
ocicl
-
Steel Bank Common Lisp
Check out ocicl as an alternative to quicklisp if you are concerned about security. Code is distributed using the OCI ecosystem (https by default, proxies work, sigstore integration, etc). https://github.com/ocicl/ocicl
-
sbcl - require
If you are willing to try switching from quicklisp to ocicl, then you'll find that ocicl *does* work with authenticating proxies on Windows. https://github.com/ocicl/ocicl
-
Ocicl – An ASDF system distribution and management tool for Common Lisp
> ... 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
What are some alternatives?
ultralisp - The software behind a Ultralisp.org Common Lisp repository
quicklisp-client - Quicklisp client.
sbcl - Mirror of Steel Bank Common Lisp (SBCL)'s official repository
ql-https - HTTPS support for Quicklisp via curl
slime - The Superior Lisp Interaction Mode for Emacs
cerberus - Common Lisp Kerberos v5 implementation
quicklisp-https
minispec - Common Lisp MiniSpec Documentation
roswell - intended to be a launcher for a major lisp environment that just works.