This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-23
Channels
- # announcements (5)
- # babashka (22)
- # beginners (240)
- # calva (51)
- # clj-commons (1)
- # cljsrn (9)
- # clojars (12)
- # clojure (81)
- # clojure-australia (2)
- # clojure-europe (40)
- # clojure-france (10)
- # clojure-italy (1)
- # clojure-nl (2)
- # clojure-uk (37)
- # clojurescript (59)
- # clojureverse-ops (2)
- # copenhagen-clojurians (1)
- # cursive (9)
- # datomic (18)
- # emacs (12)
- # fulcro (24)
- # graalvm (48)
- # hyperfiddle (5)
- # introduce-yourself (1)
- # jackdaw (1)
- # jobs (2)
- # juxt (8)
- # lsp (25)
- # malli (8)
- # missionary (1)
- # music (3)
- # off-topic (32)
- # polylith (16)
- # quil (4)
- # re-frame (52)
- # reitit (5)
- # reveal (3)
- # rewrite-clj (26)
- # rum (1)
- # sci (1)
- # shadow-cljs (14)
- # sql (2)
- # tools-build (40)
- # tools-deps (14)
- # vrac (2)
- # xtdb (63)
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.
{:deps
{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 classpathlooks ok to me, not sure why same sha matters?
gitlibs don't care
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
Like graal-config/nippy
exists in the dep expansion at two different shas etc