This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-14
Channels
- # adventofcode (38)
- # announcements (42)
- # aws (3)
- # babashka (8)
- # beginners (165)
- # calva (36)
- # chlorine-clover (14)
- # cider (6)
- # clj-kondo (5)
- # cljsrn (33)
- # clojure (27)
- # clojure-australia (1)
- # clojure-czech (1)
- # clojure-doc (1)
- # clojure-europe (26)
- # clojure-nl (6)
- # clojure-spec (6)
- # clojure-uk (3)
- # clojurescript (10)
- # code-reviews (20)
- # conjure (1)
- # core-logic (5)
- # cursive (3)
- # data-science (5)
- # datomic (35)
- # emacs (1)
- # figwheel-main (3)
- # fulcro (10)
- # honeysql (1)
- # introduce-yourself (4)
- # jobs (3)
- # jobs-discuss (4)
- # minecraft (2)
- # missionary (28)
- # nextjournal (3)
- # off-topic (45)
- # pathom (7)
- # polylith (1)
- # portal (22)
- # practicalli (2)
- # re-frame (4)
- # reagent (19)
- # releases (3)
- # remote-jobs (3)
- # reveal (1)
- # rum (4)
- # shadow-cljs (37)
- # spacemacs (14)
- # sql (1)
- # tools-build (7)
- # tools-deps (16)
- # vim (13)
- # xtdb (15)
Different topic, any user of cider-nrepl (whether it's from Emacs or e.g. Calva, vim-iced) would like to take on a smallish isolated task? I would be super grateful, it escapes a little bit my area of expertise / what I can QA myself. It boils down to wrapping up (perhaps slightly reworking) this PR, its author is on PTO (for a good reason 🎉) https://github.com/clojure-emacs/enrich-classpath/pull/8 Can explain context/requirements as needed.
I assume the -P
flag is exactly the same as using -X:deps prep
argument with the clojure
command. Are there any differences?
Does -X:deps prep
work with other aliases just as -P
does (I should probably test this myself anyway 🙂 )
No, those are different things entirely
-P does not prep dependent libs (although it will fail and tell you to prep them)
By dependent libs, do you mean the libraries that a dependency entry in a deps.edn file depends upon?
(a library that is not explicitly defined in the deps.edn file, but is a dependency of a library that is defined as a dependency)?
I feel I am still missing something in my understanding, especially the purpose / value of the -P
flag.
maybe more clearly, -P does not prep libs
-P predates that and was designed to be a flag you could prefix to whatever command you plan to run (say, in a container) to trigger all of the download and classpath construction without actually running the command
and hopefully my last annoying question, what does it mean to prep libs? Is that in relation to buildng jars from Git repos and local/root dependencies? I am not sure otherwise.
preparing source-based libs to be on the classpath if needed
Okay, that makes sense, thanks for clearing that up. Seems like there is lots more to read up on that page too 🙂
this particular point is certainly confusing and still not entirely resolved from a design perspective
My initial confusion was that they were both described as Prepare in the help and I didn't realise what an unprepared lib actually was (until now).
yes, that is the problem with using the same word for different things :)
but "prepare" is such a useful word :)
I just wasnt prepared for that 🙂