Adds option for user provided path to sbt binary for bleep import command. #382
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current bleep import command can and will not work on systems such as NixOs and Guix, so in my effort of making bleep play nice with my system I propose to add this option that lets the user provide the path to the launcher binary.
This way NixOs/Guix users are then able to provide their own sbt instances with the correct utils in scope to actually run the bleep import.
I have given this a spin and it works great!
The only caveat is that for e.g. nix flakes you need to somewhat know what you are doing and add an overlay to sbt to provide the correct tools.
If this PR (or a derivative) is merged I'll update my bleep-flake repo with the above snippet.
https://github.com/KristianAN/bleep-flake/pull/3/files