Fork me on GitHub
#tools-deps
<
2019-09-26
>
dharrigan11:09:21

Hello! Could master of tools.deps.alpha be merged into add-libs please? The add-libs is of tools.deps.alpha-0.7.541 (August 9th), not tools.deps.alpha-0.7.549 (September 17th)?

dharrigan11:09:49

Thank you very much 🙂 I guess, any reason why add-lib can't be brought in to master? It's super useful 🙂

Alex Miller (Clojure team)11:09:51

I don’t think you’re missing anything from master - just some tweaks in the specs (which aren’t used)

dharrigan11:09:24

fantastic! 🙂 Thank you (for clarifying!)

Alex Miller (Clojure team)11:09:40

There are issues with add-lib in some environments and it’s unlikely to end up included in its current form (some of it may actually be moved into Clojure itself)

dharrigan11:09:18

kk, that's good to know. Havin the ability to dynamically pull in a dep - for experimentation on the repl, is amazingly useful to have 🙂

dharrigan11:09:34

(and given clojure's great interop, doing that playing around is a very happy process!)

dominicm12:09:42

Why move it into clojure @alexmiller? Which bits?

Alex Miller (Clojure team)13:09:30

the part that tracks the current “libs” currently in use could be built in. It’s already designed to be initialized in a couple ways so even non tools.deps tools could convey the lib set via those means. add-lib itself relies on tools.deps so that probably cannot move, but the parts that update the lib set could be genetically useful

dominicm13:09:40

What's the goal of making the concept of a library first class? I can imagine using it to affect requires in different ways (e.g. Namespace versioning). Is there a set of goals in mind yet?

Alex Miller (Clojure team)13:09:06

No, none of this is baked which is why it’s on a branch

Alex Miller (Clojure team)13:09:20

There are a lot of potentially interesting things that could be done though