nixpkgs-suyu/pkgs/development/lisp-modules
R. RyanTM 1d58435501 asdf: 3.3.1 -> 3.3.2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

This update was made based on information from https://repology.org/metapackage/asdf/versions.

These checks were done:

- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 3.3.2 with grep in /nix/store/mcks1swd685sksr4yjrsyfhphzcrw9nk-asdf-3.3.2
- directory tree listing: https://gist.github.com/3a13d7343736c1454dc2701b3ea3009f
2018-05-07 05:20:34 -07:00
..
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.