nixpkgs/pkgs/development/lisp-modules
Brad Jensen 16e70997a8 Use if instead of && for deciding whether to run a command
The only difference between these forms is the return value when
"$NIX_LISP_SKIP_CODE" is the empty string.  In the original
formulation, the script would return a false exit status.  In the new
formulation, it will return a true exit status.

Its useful to be able to source cl-wrapper.sh (to get the variables it
establishes), and its a bit annoying that sourcing it with
NIX_LISP_SKIP_CODE=1 results in a false exit status.
2019-07-24 09:35:27 -07: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
quicklisp-to-nix
quicklisp-to-nix-output lispPackages.lfarm-*: init from Quicklisp 2019-03-03 13:54:08 +01: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
lisp-packages.nix lispPackages.quicklisp.quicklispdist: 2018-08-31 -> 2019-01-07 2019-01-31 07:21:30 +01: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.stumpwm: mimic Query-FS tricks for adding extra deps 2019-03-25 13:29:45 +01:00
quicklisp-to-nix-systems.txt lispPackages.lfarm-*: init from Quicklisp 2019-03-03 13:54:08 +01:00
quicklisp-to-nix.nix lispPackages.lfarm-*: init from Quicklisp 2019-03-03 13:54:08 +01:00
quicklisp.sh
README.txt
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.