Fork me on GitHub

Is this way of checking out the same git lib with multiple roots supported? It works, but I wonder if I can rely on this.

 {cheshire/cheshire {:mvn/version "5.10.0"}
  graal-config/cheshire {:git/url ""
                         :git/sha "b06e33694d2c878169958f7317ea01d9c0353ab4"
                         :deps/root "config/cheshire/cheshire"}
  graal-config/nippy {:git/url ""
                      :git/sha "b06e33694d2c878169958f7317ea01d9c0353ab4"
                      :deps/root "config/com.taoensso/nippy"}}}
The use case is having one repository with lots of native-image configurations that people can include on their classpath


as long as you use the same SHA it works, but in other cases it might not?

Alex Miller (Clojure team)18:09:40

looks ok to me, not sure why same sha matters?


can you use a different SHA for the same git/url?


if that also works, then this is :thumbsup:


I wasn't sure how they are checked out and if there could be conflicts

Alex Miller (Clojure team)18:09:17

now if you get into wanting to compare the same lib using different url/sha/whatever, things get murkier :)


this lib won't have any other deps so I don't think that will be a problem and people should really only include this dep in their final builds

Alex Miller (Clojure team)18:09:02

Like graal-config/nippy exists in the dep expansion at two different shas etc


as in: libs should not depend on this lib


but only final app users should

Alex Miller (Clojure team)18:09:39

yeah, users always do what you tell them ;)

😁 7
😂 1