@U03AU2X8TD5 I have cljr working for path management and :local/root dependencies only at this time. Even that is quite usable, to my surprise. My company is deciding on a license (EPL vs Apache vs ???) and we're expecting to release it soon. I am hoping in that time to get either git or nuget integration at least started. I had a bizarre problem with its behavior in the case of exceptions and some macro expansions which @U45FQSBF1 sleuthed and fixed just yesterday (see his latest post about the minting of alpha5 last night, and the hashing problem that finally reared its ugly head). That was quite a show stopper for any thought of releasing it, but now we're just back to "minimum viable features" and what license we want to release it under. another issue is I am currently just using the latest Clojure and not downloading a version specified in the deps file - a decision I'm weighing whether / how to change. Unlike in the JVM case, cljr acts a bit like the java.exe application for running ClojureCLR apps so, for the sake of rapid development, I tightly coupled the Clojure runtime to cljr.runtime.dll that is doing all the actual wrapping of ClojureCLR. I am not yet satisfied this is the best decision but that won't stop me from releasing it per se. Just one of the things I'm mulling over as we research which license suits us, and how to at least get git integration working. Any opinions people have about preferred OS licenses are welcome for input. I know Clojure uses EPL but the merits of it vs, say, Apache, are unclear to me. I tend toward the more liberal/less viral style of OS licenses intuitively. But we are looking into the implications of all the options.

Thanks for the update! I’d just go with Apache for the license 🙂