-
I have several scripts I'm writing that are intended to be used like normal commands. The shebang is easy enough: {:paths ["."]
:deps {org.babashka/spec.alpha {:git/url "https://github.com/babashka/spec.alpha"
:git/sha "1a841c4cc1d4f6dab7505a98ed2d532dd9d56b78"}
org.clj-commons/clj-http-lite {:mvn/version "1.0.13"}
com.cognitect/anomalies {:mvn/version "0.1.12"}
cprop/cprop {:mvn/version "0.1.19"}
failjure/failjure {:mvn/version "2.2.0"}
zprint/zprint {:mvn/version "1.2.5"}}} This works fine if I'm running it from the same directory, e.g. Unlike in https://clojureverse.org/t/help-utilizing-babashka-tasks-globally/8026/2, there are multiple bb.edn files (for good reason) in different directories, all of which are on the PATH. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 9 replies
-
@TuggyNE This is where bbin comes in: |
Beta Was this translation helpful? Give feedback.
-
A solution without bbin is the following: Write a bash wrapper script, e.g.
Make that bash wrapper script executable and put it on your path. |
Beta Was this translation helpful? Give feedback.
A solution without bbin is the following:
Write a bash wrapper script, e.g.
Make that bash wrapper script executable and put it on your path.