When executed without a devcontainer run-tool will run it via bazel, even if the tool is installed locally. Thats a waste of time, considering how slow bazel is.
At the time of writing this https://github.com/eclipse-score/devcontainer/tree/main/tools lists pre-commit with version 4.5.1. So If I have that already installed, there is no reason to run uv via bazel.
Suggested approach:
- if the tool is available, query its version. Beware that version flags are inconsistent across tools
- if the version matches exactly, use the tool directly. Future enhancement: fuzzy match, e.g. same major or same major+minor.
- add a --strict flag to the script, which will not use local tools
Note: this is labeled good first issue not because its trivial, but because it has a very clear scope.
When executed without a devcontainer
run-toolwill run it via bazel, even if the tool is installed locally. Thats a waste of time, considering how slow bazel is.At the time of writing this https://github.com/eclipse-score/devcontainer/tree/main/tools lists
pre-commitwith version4.5.1. So If I have that already installed, there is no reason to run uv via bazel.Suggested approach:
Note: this is labeled
good first issuenot because its trivial, but because it has a very clear scope.