Therefore, CLPM supports both the status quo (a Quicklisp package index
versioned by date) as well as a work in progress package index (working name
of CLPI). This new Common Lisp Package Index includes both extra metadata
about projects (such as the upstream repo which can be used to check out
development versions) and requires that systems are versioned in order to be
released.
* In-depth Documentation
...
...
@@ -195,19 +181,7 @@ is still a little rough around the edges and it may accidentally eat your files.
* Footnotes
[fn:6] On Windows, CLPM will fetch over HTTPS, but it will *not* currently
validate the certificates. See [[https://gitlab.common-lisp.net/clpm/clpm/issues/1][issue#1]] for more info.
[fn:5] All files in the primary Quicklisp distribution are served over both
[fn:1] All files in the primary Quicklisp distribution are served over both
HTTPS and HTTP, even though the Quicklisp client cannot use HTTPS itself.
[fn:4] Really, the entire project the system belongs to will be installed, but
only the dependencies of the specified system will be installed.
[fn:3] If you know a way to statically link SBCL against libc, please let me
know!
[fn:1] See, for example: [[https://www.quicklisp.org/beta/][Quicklisp]], [[https://github.com/fukamachi/qlot/][Qlot]], and [[https://github.com/CodyReichert/qi][Qi]].
[fn:2] Using the archive CL library for a full Common Lisp solution is on the
roadmap, but it needs a decent amount of work.
[fn:2] See, for example: [[https://www.quicklisp.org/beta/][Quicklisp]], [[https://github.com/fukamachi/qlot/][Qlot]], and [[https://github.com/CodyReichert/qi][Qi]].