@GrahamcOfBorg build ocamlPackages.mirage

Might be a good idea to wrap bin/mirage to add some runtime dependencies to PATH like dune.

Might make sense for dune. But won’t you also need ocaml, ocamlfind, ocamlbuild, and a handful of OCaml libraries. It seems futile to try to have them all within the wrapped mirage: so, is it better to have some but not all rather than none?

Yeah, I'm somewhat torn as well — mirage largely relies on stuff that is assumed to be installed anyways. Thus the UX for missing runtime dependencies is horrible (it shows it as command failure without any further information and you have to infer the cause from the exit code 127).

I think wrapping here could be harmful because it would limit the users choice of versions which make a difference:

• dune 1 vs. dune 2 (at least for the moment)
• different OCaml versions
• different ways of installing other dependencies (stateful opam, via a nix-shell, from nixpkgs, …) which also would in turn affect ocamlfind

I don't think that it's reasonable requiring users to use overriding to make these choices, so the simplest most user-friendly way seems to be relying on the environment.

Thanks. Let’s merge as is then.