Yes, just use deps.edn in your library and use this library from bb.edn

E.g. if you library is structured as src/my_script.clj

then add a deps.edn: {:paths ["src"}in the root of your library

and then in another project you can write in bb.edn:

{:deps {my/script {:local/root "/path/to/library"}}}

In my case the my_script.clj is just a bb.edn + a template file. So I would have 2 local repos (for simplicity sake) -- ~/aoc with bb.edn providing all the tasks and template.txt, and ~/aoc23 which will be populated with solutions for 2023. If I put {:deps {bb {:local/root "~/aoc"}}} in ~/aoc23/deps.edn would that work?

(Actually will test it rn)

ah you're using tasks?

Yes

It's a very simple bb script: https://github.com/caseneuve/aoc2023 -- I'd like to extract bb.edn and template.txt and reuse it

This will work when you add an adjacent script to your bb.edn like this:

#!/usr/bin/env bb
(require '[babashka.tasks :as tasks])
(apply tasks/run (symbol (first *command-line-args)) (rest *command-line-args*))

Right! So in order to make it less hacky, I could think about rewriting the tasks into a script that would be a dependency. But then I'd need to write the tasks for each repo again, so it's not perfect.

you don't need to do everything via tasks, what you want is probably a command line interface that you can use across projects

you can do this with babashka.cli and bb -x for example

or write a globally installed command line tool

Yeah, I'm just processing what you said and trying to get out of the tasks box :)

Is using git libraries supported as well? https://clojure.org/guides/deps_and_cli#_using_git_libraries

yes, everything that deps.edn supports