Adds common-lisp package serapeum (a dependency for Next browser as of
Next v1.4.0), using the quicklisp-to-nix mechanism.
src is overridden and pinned to 65837f8 to deal with
https://github.com/ruricolist/serapeum/issues/42
Added a wrapper package that creates symlinks to OpenSSL libraries with
the actual versions, because we have 1.0.2 with .so-suffix .1.0.0 and
cl-async-ssl is unhappy because of that.
I continue to dislike cl-postgres and simple-date upstream packaging.
* update Quicklisp distinfo
* regenerate packages
* add cl-html-parse and closure-html
* add proper mariadb library path to fix cl-mysql
* escape memoization filenames for systems
* lispPackages.cl-postgres: keep simple-date in the same package
1. Detect (and automatically handle) parasitic systems.
2. Each nix package has only one asd, and (almost) every parasitic
package inside it builds.
3. Ensure that parasitic systems are compiled.
4. Remove unnecessary testnames lisp override mechanism (the
testnae/testSystem is replaced by parasites/buildSystems).
5. Parasitic systems (if included in the system closure) become
aliases to their host package.
6. Support caching fasl files in a known directory (for faster
re-generation after modifying quicklisp-to-nix-system-info).
7. Eliminate unnecessary overrides. We're going to determine ALL
lisp dependencies correctly.
8. Don't try to "build" lisp packages with make. lispPackages should
be about bringing in a lisp library.
9. Eliminate the hand-maintained list of aliases. Parasites should
become aliases. Everything else should be a real package.
Escape things by default in derivation names (i.e. digit cannot be the
first character etc.)
Update Quicklisp (tracking upstream); list new missing dependencies
Add some minimal README about ql-to-nix
The idea is to have an almost-automatic conversion from QuickLisp, the
definitive Common Lisp package repository, to Nix. The benefit over just
using lispPackages.quicklisp is automatic installation of non-Lisp
dependencies from NixPkgs (and integration with Nix package management).
The benefit over lispPackages for normal Lisp packages is packaging just
a snapshot of QuickLisp which is known to be tested for version
compatibility between libraries.
There are some packages in lispPackages that are not from QuickLisp (for
example, the installable wrapper of QuickLisp itself). My hope is to
replace the rest with the expressions converted from QuickLisp.
Note that the current commit is a mere addition.
