tjh.dev
1Want to add a package? There are 3 simple steps!
21. Add the needed system names to quicklisp-to-nix-systems.txt.
32. cd <path to quicklisp-to-nix-systems.txt> ; nix-shell --pure --run 'quicklisp-to-nix .'
4 You might want to specify also the --cacheSystemInfoDir and --cacheFaslDir
5 parameters to preserve some data between runs. For example, it is very
6 useful when you add new packages with native dependencies and fail to
7 specify the native dependencies correctly the first time.
8 (Might be nice to ensure the cache directories exist)
93. Add native libraries and whatever else is needed to quicklisp-to-nix-overrides.nix.
10 If libraries are needed during package analysis then add them to shell.nix, too.
114. Sometimes there are problems with loading implementation-provided systems.
12 In this case you might need to add more systems in the implementation's (so
13 SBCL's) entry into *implementation-systems* in quicklisp-to-nix/system-info.lisp
14
15To update to a more recent quicklisp dist modify
16lispPackages.quicklisp to have a more recent distinfo.
17
18quicklisp-to-nix-system-info is responsible for installing a quicklisp
19package into an isolated environment and figuring out which packages
20are required by that system. It also extracts other information that
21is readily available once the system is loaded. The information
22produced by this program is fed into quicklisp-to-nix. You usually
23don't need to run this program unless you're trying to understand why
24quicklisp-to-nix failed to handle a system. The technique used by
25quicklisp-to-nix-system-info is described in its source.
26
27quicklisp-to-nix is responsible for reading
28quicklisp-to-nix-systems.txt, running quicklisp-to-nix-system-info,
29and generating the nix packages associated with the closure of
30quicklisp systems.