forked from mirrors/nixpkgs
046f091e0d
This commits needs a MAJOR audit as I oftentimes just guessed which of `$hostOffset`, `$targetOffset`, or a fixed offset should be used. |
||
|---|---|---|
| .. | ||
| asdf | ||
| clwrapper | ||
| from-quicklisp | ||
| quicklisp-to-nix | ||
| quicklisp-to-nix-output | ||
| define-package.nix | ||
| iterate.darcs-context | ||
| lisp-packages.nix | ||
| quicklisp-to-nix-overrides.nix | ||
| quicklisp-to-nix-systems.txt | ||
| quicklisp-to-nix.nix | ||
| quicklisp.sh | ||
| README.txt | ||
| shell.nix | ||
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.