This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-18
Channels
- # announcements (1)
- # babashka (16)
- # beginners (39)
- # calva (17)
- # cider (21)
- # cljs-dev (1)
- # clojars (2)
- # clojure (39)
- # clojure-australia (1)
- # clojure-europe (1)
- # clojure-spec (7)
- # conjure (1)
- # cursive (6)
- # datomic (2)
- # depstar (5)
- # graalvm (20)
- # instaparse (11)
- # meander (4)
- # pathom (4)
- # pedestal (3)
- # polylith (18)
- # re-frame (13)
- # reagent (4)
- # reitit (3)
- # shadow-cljs (2)
- # spacemacs (14)
- # vrac (1)
@ben.sless there is an issue for this but not implemented yet
I find I'm trying to implement it, one hangup I'm faced with is finding the bb
executable's path
I wonder what should happen on a lower version, throw? Only a warning? How does lein handle this?
The bb executable path: I asked about this in the GraalVM slack and someone said Graal had some API for it. I haven’t found it though
Rough sketch for an upgrade task with optional minimal version requirement. Let me know how fragile you think this is when you can
@ben.sless A few thoughts:
The thing I had in mind is just the :min-bb-version
in bb.edn
:
https://github.com/babashka/babashka/issues/663
like lein
does it. Just print a warning to stderr when you don't have the right version.
How to upgrade depends on how people installed babashka. You don't want to upgrade bb outside of the package manager if you installed it with a package manager I think?
So how to upgrade is probably a custom script that you will have locally (like the one you have) or curl-bash the standard *nix/macos install script.