Fork me on GitHub
#tools-deps
<
2019-08-31
>
sogaiu03:08:18

is the purpose of -Dclojure.libfile=... in the invocation at the end of the clojure bash (powershell) script diagnostic / for debugging?

seancorfield04:08:37

I'm not seeing anything in the code at first glance that uses it so... I don't know... but it's a good question to ask Alex when he's around (Tuesday, probably, given that it's Labor Day weekend here) @sogaiu

sogaiu04:08:54

@seancorfield tnx!

alexmiller10:08:41

It’s to communicate for add-lib or tools like it

sogaiu11:08:59

@alexmiller thanks for the explanation -- i presume it's not considered an api one can rely on (i.e. the ability to access the info via the clojure.libfile system property), is that right?

alexmiller11:08:30

It has to be considered optional. The impl in add-lib knows how to use several means to detect the lib set, including classpath introspection

alexmiller11:08:20

That whole thing is potentially something we may add to Clojure itself, tbd (which is why add-lib is not final)

cfleming11:08:59

I’d really like to use Deps as a lightweight way to manage deps for projects which aren’t always Clojure, or all Clojure. Currently there’s no way to globally exclude Clojure itself from the dependencies, correct?

cfleming11:08:45

As I understand it, in current Deps versions the system deps.edn is always read from the bundled copy in t.d.a, and there’s also no way to override that - is that correct?

cfleming11:08:11

I did try this in my deps.edn, but it didn’t work: {org.clojure/clojure {:mvn/version "1.10.1" :exclusions [org.clojure/clojure]}}

cfleming11:08:03

Would there be interest in a patch adding global exclusions support to deps, say using a top-level :exclusions key?

cfleming11:08:31

I also tried: {org.clojure/clojure {:local/root "empty"}} where empty/deps.edn is just {}, also no dice.

kenny14:08:35

Global exclusions would be very useful for us too.

alexmiller15:08:20

there is currently no way to "remove" a dependency from the top level, and clojure is included as a default dependency, so the practical effect is that clojure is always included

alexmiller15:08:53

I don't consider this to be a major problem as the in-scope use case here is running Clojure programs (I don't consider clj to be a tool for generic deps mgmt)

alexmiller15:08:47

that said, we do have a ticket for global exclusions and there certainly are times when that would be useful. similarly, it's pretty hard to use a different dep type (like local or git) to override the clojure version (due to issues in overrides of different dep type and version comparison), and that's something that I sometimes need to do

alexmiller15:08:32

anyhow, I'm still thinking about the best solution to these

cfleming20:08:26

Another use case I have is running a Clojure fork.

alexmiller21:08:24

Yeah, that’s unintentionally difficult as I discovered recently when I was trying to do something similar