Build system gardening 🪴

[ncfavier]

Warning: boring PR.

This makes cabal build 1lab-shake succeed (without warnings), so that one can build the 1Lab outside of the provided Nix shell by following the instructions in the (updated) README, should one choose to inflict this upon oneself. To prevent further bitrot in 1lab-shake.cabal, I also replaced the bespoke mkDerivation for building the shakefile with an equivalent callCabal2nix; this means that dependencies and other build options are only tracked in one place.

These changes are made with four use cases in mind:

• nix-build for building the 1Lab;
• nix-shell --run '1lab-shake all' for working on the 1Lab interactively;
• nix-shell -A shakefile --run 'cabal run 1lab-shake -- all' for working on the 1Lab and the build system interactively;
• cabal run 1lab-shake -- all outside of a Nix shell, after following the instructions in the README for setting up dependencies.

Also removes support/check.sh as discussed in #587, since the same thing can be achieved with agda --build-library.

Also bumps GHC to 9.10 to get dependencies from cache.nixos.org.

Also contains other trivial changes. The only breaking changes should be:

• The shake Cabal target is renamed to 1lab-shake.
• nix-shell -A shakefile no longer exposes ghcide (possibly other stuff as well). If needed, this can be added in shell.nix. HLS is still included.

Let me know if you find anything else.

@4e554c4c Does this work for your use cases?

[Lavenza]

Pull request preview

[4e554c4c]

Most things appear to be building, thank you

it's a bit annoying to have to manually modify cabal.project. My main concern here is accidently committing something, so I would hope that one of the three following options could be done:

1. add cabal.project to the .gitignore so change to it aren't committed
2. add the rev in support/nix/dep/Agda/github.json to cabal.project so it builds by default, and then add a check to the build script to make sure the two match, e.g.

#!/bin/sh
set -e

if [ "$(awk -F': ' '/tag/ {print $2}' cabal.project)" != "$(jq -r '.rev' support/nix/dep/Agda/github.json)" ]; then
  echo "Mismatching revs" > /dev/stderr
  exit 1;
fi

3. Parse the rev out of cabal.project with cabal2nix and use that in support/nix/dep/Agda/github.json (this one sounds like a pain).

[ncfavier]

I don't think 1 works: if I add cabal.project to .gitignore and make a change to cabal.project, git still tracks it. I think .gitignore only dictates which files become tracked in the first place, but once a file is tracked it's tracked.

2 doesn't play nicely with the third use case above: running cabal inside a Nix shell should use the Nix-provided Agda by default.

For 3, I don't think cabal2nix can do this but we could write a script using cabal-install-parsers and call it from Nix. It's a bit weird to have the information go from cabal.project to Nix though, since Nix also requires a hash that's not present in the cabal.project file. I'm also not sure this is worth the extra complexity.

[TOTBWF]

We definitely want to keep cabal.project tracked by git. @4e554c4c you can use cabal.project.local to override things, see https://cabal.readthedocs.io/en/3.4/cabal-project.html

[TOTBWF]

We can deal with synchronizing the revs in the cabal file in later work, as it looks pretty non-trivial.