This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-17
Channels
- # beginners (42)
- # cider (1)
- # cljs-dev (20)
- # clojure (73)
- # clojure-italy (8)
- # clojure-nl (53)
- # clojure-spec (11)
- # clojure-uk (88)
- # clojurescript (170)
- # clojutre (6)
- # core-async (26)
- # css (2)
- # cursive (13)
- # data-science (10)
- # datomic (15)
- # editors (3)
- # figwheel (28)
- # figwheel-main (67)
- # fulcro (57)
- # graphql (2)
- # immutant (2)
- # jobs (1)
- # jvm (4)
- # lein-figwheel (3)
- # leiningen (1)
- # off-topic (5)
- # pedestal (28)
- # re-frame (86)
- # reagent (18)
- # reitit (8)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (78)
- # spacemacs (10)
- # specter (12)
- # tools-deps (32)
- # vim (3)
Is there a way to specify an entirely different set of :deps
for an alias? (i.e. no merge, no override, just different value)
@martinklepsch in what context?
@dominicm not sure I understand what you mean by context? 😄
I’d like to swap out the value of :deps
in the top level map by another value via an alias
:override-deps
should do it, but I think there is an acknowledged bug when the override is of a different "type" (mvn/git)
@ghadi I think @martinklepsch means that he wants to have:
{:deps {A {:mvn/version "1.1.0"}}
:aliases {:B {:the-new-deps {B {:mvn/version "5.4.1"}}}}}
And when doing clj -A:B
that should result in only B
being on the classpathyeah, that’s it @dominicm
I think this has come up before -- not supported by aliases, but perhaps by a different deps.edn file
I suppose you could actually have:
{:deps {}
:aliases {:A {:extra-deps {A …}} :B {:extra-deps {B …}}}}
yeah aliases would work I think
I’m not 100% sure I need it either but I come up with some approaches and have no idea what tools-deps allows for so just asking 😄 sorry for the noise 🙂
no problem @martinklepsch not noise at all
@ghadi cool, thanks 🙂
If I specify a deps.edn with -Sdeps
any local deps.edn
in the working directory should be ignored — is that correct?
uh, yeah, especially that “final” part: “Deps data to use as the final deps file”
is there another way to achieve it then? specifying a file would also be fine, just looking for something that ignores an existing deps.edn
Hm, the word “final” creates a different expectation for me 😄 So is the only way to run a clj process with a deps.edn that’s different than the one in the current working directory to move files around?
Not that I know of. I think pack is unique in utilizing tools.deps.alpha in that way, and I'm not sure it really works due to the cwd being internal to t.d.a rather than passed in.
Maybe another option could be added
I was actually kidding :)