nixpkgs/pkgs/development/lisp-modules
John Ericson 046f091e0d treewide: Don't use envHook anymore
This commits needs a MAJOR audit as I oftentimes just guessed which of
`$hostOffset`, `$targetOffset`, or a fixed offset should be used.
2017-12-30 22:04:22 -05:00
..
asdf asdf: 3.3.0 -> 3.3.1 2017-11-20 10:46:05 +01:00
clwrapper treewide: Don't use envHook anymore 2017-12-30 22:04:22 -05:00
from-quicklisp quicklispPackages: init 2017-03-29 00:40:01 +02:00
quicklisp-to-nix asdf: 3.2.0 -> 3.3.0 2017-11-11 15:31:43 +01:00
quicklisp-to-nix-output lispPackages.cl-protobufs: init at 20170403-git 2017-09-27 09:07:26 -07:00
define-package.nix lispPackages: A less aggressive way to manipulate ASDF search path, as suggested by Fare 2017-11-22 07:56:17 +01:00
iterate.darcs-context Update iterate lisp package 2014-11-13 11:17:48 +03:00
lisp-packages.nix quicklisp-to-nix: make it possible to run with Nix sandboxing enabled 2017-09-04 21:39:07 +02:00
quicklisp-to-nix-overrides.nix lispPackages: A less aggressive way to manipulate ASDF search path, as suggested by Fare 2017-11-22 07:56:17 +01:00
quicklisp-to-nix-systems.txt lispPackages.cl-protobufs: init at 20170403-git 2017-09-27 09:07:26 -07:00
quicklisp-to-nix.nix lispPackages.cl-protobufs: init at 20170403-git 2017-09-27 09:07:26 -07:00
quicklisp.sh quicklisp (lispPackages.quicklisp): init 2016-03-25 17:58:05 +01:00
README.txt Update the ql-to-nix readme 2017-08-31 20:10:19 -07:00
shell.nix lispPackages: add clsql-postgresql* 2017-09-04 21:39:07 +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.