Fork me on GitHub
#babashka
<
2020-10-18
>
hugod12:10:50

A couple of questions on glam: i) could glam be made self-installable? i.e. use clojure -Sdeps with the glam package to install the glam binary ii) when using glam as a package manager outside the context of a shell, is there a way to get the path of just a single tool (either from cache or have it installed as a side effect)?

borkdude14:10:50

@ What context is ii - the JVM / bb?

borkdude14:10:20

Can you give more info? I think i) is easy to support, we just have to add a package for glam itself

hugod00:10:39

For ii, I’m using glam to provide repeatable tool versions for makejack, Makejack invokes tools directly without using.a shell, The new glam.edn file can be used to fix the version of the tool. Currently it uses the install command and parses the output path string to get the tool’s path. Ideally makejack would be able to install tools whether or not glam has been explicitly installed by the user. It currently use clojure to install a babashka version, then uses babashka to run glam.

borkdude10:10:37

@ I'm not sure if glam will stay compatible with babashka - I think the way forward is to use the dedicated binary or glam as a JVM lib. So for ii you would then install glam-bin rather than babashka.

borkdude10:10:59

Could you make issues about this? I would be happy to support it.

borkdude16:10:19

API docs for babashka.process: https://github.com/babashka/process#api Will be part of 0.2.3