This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-12
Channels
- # adventofcode (6)
- # announcements (10)
- # beginners (70)
- # boot (55)
- # calva (15)
- # cljs-dev (18)
- # clojure (32)
- # clojure-europe (4)
- # clojure-nl (2)
- # clojure-spec (20)
- # clojure-uk (6)
- # clojurescript (14)
- # cursive (11)
- # datomic (31)
- # figwheel-main (7)
- # fulcro (1)
- # incanter (1)
- # jobs-discuss (3)
- # juxt (1)
- # off-topic (17)
- # onyx (5)
- # pathom (3)
- # pedestal (2)
- # quil (20)
- # re-frame (6)
- # reitit (1)
- # ring (2)
- # rum (5)
- # shadow-cljs (73)
- # spacemacs (5)
- # tools-deps (11)
- # uncomplicate (1)
- # unrepl (1)
- # yada (11)
Hi, I was wondering if you have thought about adding clojure CLI to SDKMAN https://sdkman.io. I had a conversation with the main author Marco Vermeulen in https://gitter.im/sdkman/cli-dev and he needs a tarball that is usable by just untar. Leiningen added the support while ago. Plz check out https://github.com/technomancy/leiningen/issues/2204
one tricky thing in the clj script is that the script gets modified on install to point to the absolute location of the lib dir
not sure what the best way to handle that is
but feel free to file an issue at https://dev.clojure.org/jira/browse/TDEPS
would be happy to add it but I’m not going to have time to work on it, some whatever help you could provide would be useful
the current install is basically a tar file plus an install script that mostly just moves files around, but also makes the jar location replacement mentioned above
@alexmiller Created https://dev.clojure.org/jira/browse/TDEPS-113 I’m happy to help this out. Should I enhance https://github.com/clojure/brew-install by creating a PR to add another package.sh for SDKMAN under script
dir, or following the contribution workflow and sign the CA?
We don’t do PRs in this repo so patch on the jira would be better
And ca is required
See https://clojure.org/community/contributing for the process @kenji_signifier if you haven't already seen it...
thx @alexmiller and @seancorfield I’ll follow the workflow once I create a patch for it.