I just published a release: https://github.com/kloimhardt/babashka/releases/tag/v0.2.2
I would suggest you to maintain the versions in sync. Under v0.2.2 there should be babashka-0.2.2-windows-amd64.zip Also I'll come with the something in scoop and we can tune it to a level it's convenient.
@markus.agwin I think it would maybe be good if you renamed the executable and zip archive to something that doesn't conflict with the "official" babashka
like bb-web.exe and babashka-web.zip
I‘ll take care of the naming and come back. thank you for the feedback. Any hints where to look to set the names as I need to figure out how to do that (tomorrow)
The name is determined in the script/compile scripts
it would be nice to dodge also binary conflicts. Technically binary sits in it's own directory, but having bb-web.exe
would be nicer as well.
that's what I proposed as well
Oh, sorry I overlooked this
so then it must be a good idea :)
I can dodge this by setup shim in scoop, but still valid since, also users can just download, uncompress and copy to some PATH to use it side-by side with original babashka
yes, let's just avoid confusion all around
understood, will come back with a new release attempt as basis for further steps
This is how it may look like (draft PR) https://github.com/littleli/scoop-clojure/pull/117