I see. Thanks! So for now, if I'd like to publish it to enable others to use it, I would have to publish a forked version of tools.deps.alpha with my extension worked into the codebase?

No. They would just require your namespace which extends the multi method

Hm, but if this is not exposed to do in the cli, it feels like a workaround at best, only for people who are using deps as a library. Not sure how the common use case looks for using deps (as I'm still mostly using leiningen), but feels like most people would still stick to using the cli. But again, I don't know enough about this to say for sure

In that case you'll need to fork the cli

alright. Thanks a lot for the explanations!

What’s your extension?

@U064X3EF3 fetching dependencies via a content-addressed database (IPFS or similar) and splitting versions into two different versions, one for the interface and one for the implementation

Including an extension would just require changing the one line in the clojure script that defined the tools classpath

Well, I guess the extension also needs to be loaded

clj has been out for 2 or 3 years and this is the first time someone has asked about this so it hasn’t really been a priority

yeah, if I'll fork tools.deps I can see the path forward easily, but for obvious reasons I wanted to avoid that. Makes sense that no one asked, as it's a bit bleeding-edge stuff to load dependencies from something that is not HTTP/S Thanks Alex!

I think it gets more complex if you want to support dependencies which depend on an extension.

Hm, yeah, might have to have some sort of bootstrapping available or ship whatever the extension comes with over clojars/maven. Unless I just end up with a external babashka cli util that does the fetching... Not sure yet, exploring the options

Figuring all that out is why we haven’t done it yet :)