nixpkgs/pkgs/development/lisp-modules
2020-10-24 11:43:31 +02:00
..
asdf asdf: don't restrict to linux, since darwin works too 2020-08-08 14:31:57 +12:00
clwrapper lispPackages: fix build 2019-11-22 17:41:46 +01:00
from-quicklisp
quicklisp-to-nix quicklisp-to-nix: preload some implementation-provided dependencies 2020-10-24 11:42:33 +02:00
quicklisp-to-nix-output lispPackages: update distinfo 2020-03-15 22:34:16 +01:00
define-package.nix lisp-modules: fix missing && after test command 2020-05-04 21:55:21 +02:00
lisp-packages.nix quicklisp: update distinfo 2019-12-27 -> 2020-10-16 2020-10-24 10:32:58 +02: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.cl-store: fix build 2020-02-04 17:22:12 +01:00
quicklisp-to-nix-systems.txt lispPackages: add serapeum 2020-01-20 18:35:49 -10:00
quicklisp-to-nix.nix lispPackages: update distinfo 2020-03-15 22:34:16 +01:00
quicklisp.sh lispPackages.quicklisp: update shell script to avoid RO FS with new caching behaviour 2020-10-24 11:30:52 +02:00
README.txt quicklisp-to-nix: README: Mention caches 2020-10-24 11:43:31 +02: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 .'
  You might want to specify also the --cacheSystemInfoDir and --cacheFaslDir
  parameters to preserve some data between runs. For example, it is very
  useful when you add new packages with native dependencies and fail to
  specify the native dependencies correctly the first time.
  (Might be nice to ensure the cache directoris exist)
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.