grapevine/xtask
Benjamin Lee f76806655f
xtask-specific binaries in GRAPEVINE_XTASK_PATH
Some possible alternatives to this:

 - Keep putting them in PATH.
 - Make xtask a nix derivation. We would lose out on incremental
   compilation this way, and would end up recompiling xtask from scratch
   whenever something in the main package changed.
 - Have xtask call `nix build --inputs-from $toplevel nixpkgs#go` and
   such. Slow and tedious.
2024-09-24 15:42:11 -07:00
..
src xtask-specific binaries in GRAPEVINE_XTASK_PATH 2024-09-24 15:42:11 -07:00
Cargo.toml add live progress display to complement wrapper 2024-09-24 11:25:52 -07:00