Fork me on GitHub
#babashka
<
2023-05-13
>
Aziz Aldawood14:05:13

is there a similar functionality to sync-deps in babashka? (i.e. add dep to bb.edn and call sync-deps so I don't have to reload the repl)

borkdude14:05:52

There is (and has been for a long time)

(babashka.deps/add-deps '{:deps ...})

borkdude14:05:02

If you want sync-deps you can just slurp the bb.edn in there

Aziz Aldawood14:05:44

I have used add-deps before, never thought about slurping though. will try it now

borkdude14:05:01

oh and also parse it as EDN with clojure.edn/read-string

Aziz Aldawood14:05:09

I don't this work pods though

Aziz Aldawood14:05:04

I have a pod in my bb.edn

borkdude14:05:08

yeah that won't work (yet) but you can manually load it using (babashka.pods/load-pod symbol version)

Aziz Aldawood14:05:18

I did that, it's not an issue. I was just being lazy

borkdude14:05:26

I hope to provide a better support for pods in dependencies later on, not through bb.edn but via a manifest in the dependencies

borkdude14:05:42

which pod are you currently using?

Aziz Aldawood14:05:07

postgresql

👍 2
Aziz Aldawood14:05:46

when you say manifest do you mean something instead of :mvn/version ?

borkdude14:05:13

pods have a manifest that describe where to fetch the binaries, that's what I'm talking about

borkdude14:05:30

normally the manifest is looked up via the pod registry

borkdude14:05:34

which is centralized

borkdude14:05:11

but the idea is to decentralize it so you can put the manifest in a dependency

👍 2