nixpkgs/pkgs/development/lisp-modules
2019-08-27 16:36:47 +02:00
..
asdf asdf: 3.3.2 -> 3.3.3 2019-07-14 22:05:31 -07:00
clwrapper Use if instead of && for deciding whether to run a command 2019-07-24 09:35:27 -07:00
from-quicklisp quicklispPackages: init 2017-03-29 00:40:01 +02:00
quicklisp-to-nix lispPackages: update to Quicklisp release 2019-07-11 2019-08-25 22:53:27 +03:00
quicklisp-to-nix-output lispPackages: update to Quicklisp release 2019-07-11 2019-08-25 22:53:27 +03:00
define-package.nix treewide: use ${stdenv.shell} instead of /bin/sh where possible 2019-01-16 20:37:15 +01:00
iterate.darcs-context Update iterate lisp package 2014-11-13 11:17:48 +03:00
lisp-packages.nix Merge master into staging-next 2019-08-27 16:36:47 +02:00
openssl-lib-marked.nix lispPackages.quicklisp: 2018-04-30 -> 2018-08-31 ; regenerate packages 2018-09-12 11:52:43 +03:00
quicklisp-to-nix-overrides.nix lispPackages: update to Quicklisp release 2019-07-11 2019-08-25 22:53:27 +03:00
quicklisp-to-nix-systems.txt lispPackages.lfarm-*: init from Quicklisp 2019-03-03 13:54:08 +01:00
quicklisp-to-nix.nix lispPackages: update to Quicklisp release 2019-07-11 2019-08-25 22:53:27 +03: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.quicklisp: 2018-04-30 -> 2018-08-31 ; regenerate packages 2018-09-12 11:52:43 +03: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.