Preliminary release notes for 0.2.1: https://github.com/borkdude/babashka/blob/master/CHANGELOG.md
@borkdude when I'm running the Babashka installer, will it automatically pickup v0.2.1 on new builds?
Yes
It isn’t release yet
kk. I'm just trying to decide if I should be thinking about locking down versions or not in case something becomes backwards incompatible six years from now
@borkdude is there a template repo for a babashka pod?
@goomba I think we could support that in the installer script via a --version
flag:
https://github.com/borkdude/babashka/blob/master/install
Note that clj-kondo already has this: https://github.com/borkdude/clj-kondo/blob/master/script/install-clj-kondo
Feel free to contribute that change. I think we should move to flags for everything (while keeping the dir argument backwards compatible)
here @borkdude https://github.com/borkdude/babashka/pull/598
Thanks. Two questions: - Why the change for /tmp/bb instead of /usr/local/bin? - Does it still support the old way, i.e. only passing a directory name without flags?
dman, /tmp/bb was i tried that and came by mistake
it should.
$ ~/Downloads/install.txt /tmp
Installs latest (or specific) version of babashka. Installation directory defaults to /usr/local/bin.
I think what should happen is that if there's only one argument, it is interpreted as the dir. Else use flags
Else this will break existing users
:thinking_face:
You don't understand?
i got that - let me add the fix around this. I confused with ~/Downloads/install.txt /tmp
yeah sorry, Chrome downloads things as .txt. I don't know how to turn that off
oh ok.
only this specific combination need to be covered right for backward compatibility, right? How does this look now
I tested it and it works
thanks
I'll make an issue for that
@alekcz360 I don't know of a template, but you could take any existing project as an example: https://github.com/borkdude/babashka/blob/master/doc/libraries.md#pods General docs are here: https://github.com/babashka/babashka.pods
w00t! I'll jump on it