nixpkgs/pkgs/development/lisp-modules
Taylor Viti 418b80bd88 lispPackages: add serapeum
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
2020-01-20 18:35:49 -10:00
..
asdf asdf: 3.3.2 -> 3.3.3 2019-07-14 22:05:31 -07:00
clwrapper lispPackages: fix build 2019-11-22 17:41:46 +01:00
from-quicklisp quicklispPackages: init 2017-03-29 00:40:01 +02:00
quicklisp-to-nix A band-aid workaround for 68384. The situation should not be possible, not clear whether there is a missed detail about ASDF or SBCL 2019-09-30 18:26:08 +02:00
quicklisp-to-nix-output lispPackages: add serapeum 2020-01-20 18:35:49 -10:00
define-package.nix lispPackages: fix build 2019-11-22 17:41:46 +01:00
iterate.darcs-context
lisp-packages.nix treewide: remove redundant rec 2019-08-28 11:07:32 +00:00
openssl-lib-marked.nix treewide: Get rid of most parseDrvName without breaking compat 2019-11-24 17:22:28 +00:00
quicklisp-to-nix-overrides.nix lispPackages: add serapeum 2020-01-20 18:35:49 -10:00
quicklisp-to-nix-systems.txt lispPackages: add serapeum 2020-01-20 18:35:49 -10:00
quicklisp-to-nix.nix lispPackages: add serapeum 2020-01-20 18:35:49 -10:00
quicklisp.sh
README.txt Update the ql-to-nix readme 2017-08-31 20:10:19 -07:00
shell.nix Re-Revert "Merge branch 'staging-next'" 2019-09-22 09:38:09 +02:00

Want to add a package?  There are 3 simple steps!
1. Add the needed system names to quicklisp-to-nix-systems.txt.
2. cd <path to quicklisp-to-nix-systems.txt> ; nix-shell --run 'quicklisp-to-nix .'
3. Add native libraries and whatever else is needed to quicklisp-to-nix-overrides.nix.

To update to a more recent quicklisp dist modify
lispPackages.quicklisp to have a more recent distinfo.

quicklisp-to-nix-system-info is responsible for installing a quicklisp
package into an isolated environment and figuring out which packages
are required by that system.  It also extracts other information that
is readily available once the system is loaded.  The information
produced by this program is fed into quicklisp-to-nix.  You usually
don't need to run this program unless you're trying to understand why
quicklisp-to-nix failed to handle a system.  The technique used by
quicklisp-to-nix-system-info is described in its source.

quicklisp-to-nix is responsible for reading
quicklisp-to-nix-systems.txt, running quicklisp-to-nix-system-info,
and generating the nix packages associated with the closure of
quicklisp systems.