tvl-depot/users/sterni/clhs-lookup/default.nix

{ pkgs, depot, ... }:

let
  inherit (pkgs) fetchzip writeText;
  inherit (depot.nix) buildLisp;
  inherit (builtins) replaceStrings;

  clhsVersion = "7-0";

  clhs = fetchzip {
    name = "HyperSpec-${replaceStrings [ "-" ] [ "." ] clhsVersion}";
    url = "ftp://ftp.lispworks.com/pub/software_tools/reference/HyperSpec-${clhsVersion}.tar.gz";
    sha256 = "1zsi35245m5sfb862ibzy0pzlph48wvlggnqanymhgqkpa1v20ak";
    stripRoot = false;
  };

  clhs-path = writeText "clhs-path.lisp" ''
    (in-package :clhs-lookup.clhs-path)
    (defparameter *clhs-path* (pathname "${clhs}/"))
  '';

  clhs-lookup = buildLisp.program {
    name = "clhs-lookup";

    deps = [
      {
        default = buildLisp.bundled "asdf";
        sbcl = buildLisp.bundled "uiop";
      }
    ];

    srcs = [
      ./packages.lisp
      clhs-path
      ./clhs-lookup.lisp
    ];
  };
in
clhs-lookup
feat(sterni/clhs): add cli to lookup symbols in the CLHS Probably very similar to M-x sly-hyperspec-lookup: take a list of common lisp symbols on the command line open the corresponding pages in a local copy of the hyperspec in $BROWSER. Optionally the paths can be printed to stdout. Change-Id: I389e254f14eb0fc8fd8b18a4dbfe7adeeda9ba72 Reviewed-on: https://cl.tvl.fyi/c/depot/+/2397 Tested-by: BuildkiteCI Reviewed-by: sterni <sternenseemann@systemli.org> 2021-01-14 22:57:07 +01:00			`{ pkgs, depot, ... }:`

			`let`
			`inherit (pkgs) fetchzip writeText;`
			`inherit (depot.nix) buildLisp;`
			`inherit (builtins) replaceStrings;`

			`clhsVersion = "7-0";`

			`clhs = fetchzip {`
			`name = "HyperSpec-${replaceStrings [ "-" ] [ "." ] clhsVersion}";`
			`url = "ftp://ftp.lispworks.com/pub/software_tools/reference/HyperSpec-${clhsVersion}.tar.gz";`
			`sha256 = "1zsi35245m5sfb862ibzy0pzlph48wvlggnqanymhgqkpa1v20ak";`
			`stripRoot = false;`
			`};`

			`clhs-path = writeText "clhs-path.lisp" ''`
			`(in-package :clhs-lookup.clhs-path)`
			`(defparameter clhs-path (pathname "${clhs}/"))`
			`'';`

			`clhs-lookup = buildLisp.program {`
			`name = "clhs-lookup";`

			`deps = [`
feat(nix/buildLisp): add ecl Adds ECL as a second supported implementation, specifically a statically linked ECL. This is interesting because we can create statically linked binaries, but has a few drawbacks which doesn't make it generally useful: * Loading things is very slow: The statically linked ECL only has byte compilation available, so when we do load things or use the REPL it is significantly worse than with e. g. SBCL. * We can't load shared objects via the FFI since ECL's dffi is not available when linked statically. This means that as it stands, we can't build a statically linked //web/panettone for example. Since ECL is quite slow anyways, I think these drawbacks are worth it since the biggest reason for using ECL would be to get a statically linked binary. If we change our minds, it shouldn't be too hard to provide ecl-static and ecl-dynamic as separate implementations. ECL is LGPL and some libraries it uses as part of its runtime are as well. I've outlined in the ecl-static overlay why this should be of no concern in the context of depot even though we are statically linking. Currently everything is building except projects that are using cffi to load shared libaries which have gotten an appropriate `badImplementations` entry. To get the rest building the following changes were made: * Anywhere a dependency on UIOP is expressed as `bundled "uiop"` we now use `bundled "asdf"` for all implementations except SBCL. From my testing, SBCL seems to be the only implementation to support using `(require 'uiop)` to only load the UIOP package. Where both a dependency on ASDF and UIOP exists, we just delete the UIOP one. `(require 'asdf)` always causes UIOP to be available. * Where appropriate only conditionally compile SBCL-specific code and if any build the corresponding files for ECL. * //lisp/klatre: Use the standard condition parse-error for all implementations except SBCL in try-parse-integer. * //3p/lisp/ironclad: disable SBCL assembly optimization hack for all other platforms as it may interfere with compilation. * //3p/lisp/trivial-mimes: prevent call to asdf function by substituting it out of the source since it always errors out in ECL and we hardcode the correct path elsewhere anyways. As it stands ECL still suffers from a very weird problem which happens when compiling postmodern and moptilities: https://gitlab.com/embeddable-common-lisp/ecl/-/issues/651 Change-Id: I0285924f92ac154126b4c42145073c3fb33702ed Reviewed-on: https://cl.tvl.fyi/c/depot/+/3297 Tested-by: BuildkiteCI Reviewed-by: tazjin <mail@tazj.in> Reviewed-by: eta <tvl@eta.st> 2021-08-09 02:47:07 +02:00			`{`
			`default = buildLisp.bundled "asdf";`
			`sbcl = buildLisp.bundled "uiop";`
			`}`
feat(sterni/clhs): add cli to lookup symbols in the CLHS Probably very similar to M-x sly-hyperspec-lookup: take a list of common lisp symbols on the command line open the corresponding pages in a local copy of the hyperspec in $BROWSER. Optionally the paths can be printed to stdout. Change-Id: I389e254f14eb0fc8fd8b18a4dbfe7adeeda9ba72 Reviewed-on: https://cl.tvl.fyi/c/depot/+/2397 Tested-by: BuildkiteCI Reviewed-by: sterni <sternenseemann@systemli.org> 2021-01-14 22:57:07 +01:00			`];`

			`srcs = [`
			`./packages.lisp`
			`clhs-path`
			`./clhs-lookup.lisp`
			`];`
			`};`
feat(users/sterni): move clhs.clhs-lookup to clhs-lookup This way ci should pick up on clhs-lookup since only a single derivation is exposed with the default.nix and it is less cumbersome to type the attribute path (users.sterni.clhs.clhs-lookup → users.sterni.clhs-lookup). The exposed CLHS wasn't used for anything anyways and I can always expose it again using passthru or extra if it's ever merged. Change-Id: I6c5aeba1b58ca650700c6efa0913e4b42685ea6b Reviewed-on: https://cl.tvl.fyi/c/depot/+/2461 Tested-by: BuildkiteCI Reviewed-by: sterni <sternenseemann@systemli.org> 2021-01-29 18:22:51 +01:00			`in`
			`clhs-lookup`