Qi: a Simple Package Manager for Common Lisp

If the author shows up, as one of a few here who wants to know, why YAML? In other languages YAML parsers are a dime-a-dozen affair, while the same is true of SEXP&#x2F;EDNish type stuff so proudly mocked in Lispland by insiders and outsiders alike.<p>Was it personal preference or something more? I scanned your stuff, but did not see anything insightful on the landing page.

I&#x27;m not sure I understand what this is providing over QuickLisp and QuickProject. Version pinning seems useful, but I don&#x27;t see an explanation of how it&#x27;s being done, and I don&#x27;t understand how it can work with a REPL. It seems like it would be better to handle it in asdf and QuickLisp. Using YAML also seems like a poor choice for Common Lisp, where everything is s-expressions.<p>Also, there&#x27;s already a Common Lisp project named &quot;Qi&quot;: <a href="http:&#x2F;&#x2F;cliki.net&#x2F;Qi" rel="nofollow">http:&#x2F;&#x2F;cliki.net&#x2F;Qi</a>

This looks pretty cool. It sounds like it can wrap Quicklisp, which is real good considering how much work and apprecation there is for @xach re the Quicklisp work. He also expects to have a big donor announcement status announcement in a few days, according to blog.quicklisp.org.<p>This seems like it is not just a package manager, but maybe like a project manager, between Quicklisp and cl-project?<p>Anyway, every few months I am happy to get back into the CL scene. There is something I cannot get me to move away from the dark arts of Lisp!

This seems to focus more on project lifecycles and scaffolding than Roswell (my current go-to toplevel for Common Lisp).<p>I&#x27;m not sure about using yml to track dependencies, those should be in the asdf file, although I guess this is to enable pinning etc.