babashka

https://github.com/babashka/babashka. Also see #sci, #nbb and #babashka-circleci-builds .
Markus Agwin 2020-10-07T13:29:11.284300Z

I just published a release: https://github.com/kloimhardt/babashka/releases/tag/v0.2.2

littleli 2020-10-07T15:22:19.284600Z

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.

borkdude 2020-10-07T15:27:52.284800Z

@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

borkdude 2020-10-07T15:28:07.285Z

like bb-web.exe and babashka-web.zip

Markus Agwin 2020-10-07T15:31:56.288300Z

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)

borkdude 2020-10-07T15:32:24.288500Z

The name is determined in the script/compile scripts

littleli 2020-10-07T15:36:31.288700Z

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.

borkdude 2020-10-07T15:36:58.288900Z

that's what I proposed as well

littleli 2020-10-07T15:37:21.289100Z

Oh, sorry I overlooked this

borkdude 2020-10-07T15:37:31.289300Z

so then it must be a good idea :)

littleli 2020-10-07T15:38:42.289500Z

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

borkdude 2020-10-07T15:39:36.289700Z

yes, let's just avoid confusion all around

Markus Agwin 2020-10-07T20:57:55.291500Z

understood, will come back with a new release attempt as basis for further steps

littleli 2020-10-07T21:29:32.291700Z

This is how it may look like (draft PR) https://github.com/littleli/scoop-clojure/pull/117