ci: use nix build

Author: doyougnu

.github/workflows/deploy.yml

@@ -9,11 +9,9 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2.4.0
-    - uses: cachix/install-nix-action@v16
-      with:
-        nix_path: nixpkgs=channel:nixos-unstable
-    - run: nix-shell --run 'cabal update; make clean; make html SPHINXOPTS="-W"'
+    - uses: actions/checkout@v3
+    - uses: cachix/install-nix-action@v22
+    - run:  nix build
     - name: Deploy 🚀
       uses: JamesIves/github-pages-deploy-action@v4.2.2
       with:

Makefile

@@ -7,7 +7,6 @@ SPHINXOPTS    ?=
 SPHINXBUILD   ?= sphinx-build
 SOURCEDIR     = .
 BUILDDIR      = _build
-SOURCE_DATE_EPOCH = $(shell git log -1 --format=%ct)
 
 # Put it first so that "make" without argument is like "make help".
 help:

flake.lock

@@ -32,12 +32,13 @@ pkgs.stdenv.mkDerivation {
    buildInputs = pythonInputs ++ nonPythonInputs;
 
    preBuild = ''
-   export SOURCE_DATE_EPOCH="$(${pkgs.coreutils}/bin/date '+%s')"
-   pip list
+   unset SOURCE_DATE_EPOCH
   '';
 
    buildPhase = ''
    runHook preBuild
+   SOURCE_DATE_EPOCH="$(${pkgs.coreutils}/bin/date '+%s')"
+   make clean
    make ${target} SPHINXOPTS="-W"
    touch "_build/.nojekyll"
    touch "_build/html/.nojekyll"

hoh.nix

@@ -19,11 +19,11 @@ structures and closing memory leaks; any intermediate level Haskeller should be
 able to follow along. After reading this chapter, a reader should be able to
 spot inefficient data structure use by reading code, and GHC's profiling tools
 to diagnose memory performance issues and identify hot code. To read through the
-code, this `commit
-<https://github.com/gelisam/klister/commit/33501b2233ce865407a8a3ca7c090457f3375442>`
-is the result of the case study, and `here
-<https://github.com/gelisam/klister/tree/5aea4d2b9df8f6e9db276078570c1e1bd1306cd3>`
-is the state of the klister code base that the tutorial starts with.
+code, `this commit
+<https://github.com/gelisam/klister/commit/33501b2233ce865407a8a3ca7c090457f3375442>`__
+is the result of the case study, and `this commit
+<https://github.com/gelisam/klister/tree/5aea4d2b9df8f6e9db276078570c1e1bd1306cd3>`__
+was the state of the klister code base that the tutorial starts with.
 
 The rest of the chapter is structured as follows. We introduce the |klister|
 interpreter and perform a performance minded code review. We then use the