Today the ctx.bazel machinery expects that the user has a bazel on their $PATH somewhere. Ideally the Aspect CLI would do the right thing and mostly stand alone, which means provisioning a bazelisk transparently by default.
- Add a new
cache.axl implementation transliterating the current cache crate
- Add a new
bazelisk.axl implementation which consumes the current HTTP feature(s) and the cache package to provide a helper for downloading a bazelisk binary
- Extend the reference
config.axl to use the bazelisk.axl and install a bazel binary into the config struct.
- Extend the
ctx.bazel machinery to go through the config struct to get the path of the bazel nominal binary.
Today the
ctx.bazelmachinery expects that the user has abazelon their$PATHsomewhere. Ideally the Aspect CLI would do the right thing and mostly stand alone, which means provisioning abazelisktransparently by default.cache.axlimplementation transliterating the currentcachecratebazelisk.axlimplementation which consumes the current HTTP feature(s) and thecachepackage to provide a helper for downloading abazeliskbinaryconfig.axlto use thebazelisk.axland install abazelbinary into the config struct.ctx.bazelmachinery to go through the config struct to get the path of thebazelnominal binary.