qlot
distribution-spec
qlot | distribution-spec | |
---|---|---|
9 | 54 | |
384 | 747 | |
- | 3.3% | |
9.7 | 7.8 | |
2 days ago | 10 days ago | |
Common Lisp | Go | |
MIT License | Apache License 2.0 |
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.
distribution-spec
-
The transitory nature of MLOps: Advocating for DevOps/MLOps coalescence
Back in 2013, a little company called Docker made it really easy to start using containers to package up applications. A big key to their success was the OCI (you can learn about that here), an industry wide initiative to have standards around how we package up our applications. Because of OCI standards, we have hundreds (maybe thousands?) of tools that can be combined to manage and deploy applications. So why arenβt we using this for packaging up Notebooks and AI models as well? It would make deploying, sharing, and managing our models easier for everyone involved.
-
The Road To Kubernetes: How Older Technologies Add Up
Kubernetes on the backend used to utilize docker for much of its container runtime solutions. One of the modular features of Kubernetes is the ability to utilize a Container Runtime Interface or CRI. The problem was that Docker didn't really meet the spec properly and they had to maintain a shim to translate properly. Instead users could utilize the popular containerd or cri-o runtimes. These follow the Open Container Initiative or OCI's guidelines on container formats.
-
Coexistence of containers and Helm charts - OCI based registries
OCI stands for Open Container Initiative, and its goal as an organization is to define a specification for container formats and runtime.
-
Bazzite β a Steam0S-like OCI image for desktop, living room, and handheld PCs
https://opencontainers.org/
Here is Containerfile from the repo: https://github.com/ublue-os/bazzite/blob/main/Containerfile
-
Distroless images using melange and apko
apko allows us to build OCI container images from .apk packages.
- OCI image from dockerfile
- Fat OCI images are a cultural problem
-
Progressive Delivery on AKS: A Step-by-Step Guide using Flagger with Istio and FluxCD
Flagger's load testing service can be installed via a Kustomization resource based on manifests packaged as an artifact in an Open Container Initiative (OCI) registry
-
Creating Kubernetes Cluster With CRI-O
CRI-O is a lightweight container runtime for Kubernetes. It is an implementation of Kubernetes CRI to use Open Container Initiative (OCI) compatible runtimes for running pods. It supports runc and Kata Containers as the container runtimes, but any OCI-compatible runtime can be integrated.
-
What is the current status of Docker and how far is it from getting ported?
So somebody else created runj (runj is an experimental, proof-of-concept OCI-compatible runtime for FreeBSD jails.) https://github.com/samuelkarp/runj
What are some alternatives?
ultralisp - The software behind a Ultralisp.org Common Lisp repository
jib - π Build container images for your Java applications.
sbcl - Mirror of Steel Bank Common Lisp (SBCL)'s official repository
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
slime - The Superior Lisp Interaction Mode for Emacs
proxmox-lxc-idmapper - Proxmox unprivileged container/host uid/gid mapping syntax tool.
ql-https - HTTPS support for Quicklisp via curl
appleprivacyletter - An open letter against Apple's new privacy-invasive client-side content scanning.
minispec - Common Lisp MiniSpec Documentation
dive - A tool for exploring each layer in a docker image
quicklisp-https
bartholomew - The Micro-CMS for WebAssembly and Spin