This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-17
Channels
- # announcements (7)
- # beginners (9)
- # calva (17)
- # clj-kondo (11)
- # clojure (68)
- # clojure-austin (2)
- # clojure-bay-area (3)
- # clojure-europe (19)
- # clojure-gamedev (10)
- # clojure-nl (1)
- # clojure-norway (73)
- # clojure-spec (5)
- # clojure-uk (5)
- # clojuredesign-podcast (6)
- # clojurescript (65)
- # community-development (28)
- # conjure (1)
- # datahike (34)
- # datomic (36)
- # emacs (11)
- # funcool (1)
- # helix (13)
- # honeysql (36)
- # hyperfiddle (15)
- # jobs (1)
- # jobs-discuss (4)
- # malli (13)
- # nbb (21)
- # off-topic (51)
- # practicalli (20)
- # reitit (1)
- # releases (1)
- # ring (4)
- # squint (1)
- # tools-deps (14)
- # transit (8)
Since git deps are checked out before being used, could clj -X:deps prep
also work on them?
Yes, it does
Perhaps a dumb question, but is it possible to run a tool without installing it first? I’m imagining something like this:
clojure -Ttools run nvd-clojure/nvd-clojure '{:mvn/version "3.4.0"}' nvd.task/check
This is for CI/scripting, where I’d prefer not to have a separate install step from running the toolNamed tools are installed by definition
You can use a tool alias though
Do you need -T or just -X?
If you want to both install and run, that’s going to be two commands
I want to run https://github.com/namenu/deps-diff, without using the content of my deps.edn file in the classpath, so I think as -T?
@U051KLSJF There's no entry point to run that via -T
or -X
with paths to EDN files. It has a GH action that invokes the CLI twice to produce deps trees and then compares those as EDN: https://github.com/namenu/deps-diff/blob/main/action.yml#L64-L89
(I mean, yes, there's a -X
entrypoint the action uses but you need to run two CLI commands first to prep the data)
Yup, I need to fork it to get it to run its own diff as a tool. Currently, it is running as clojure -Sdeps
which means that everything in the deps.edn is also included in the classpath, which is causing issues in our case
The other issue with installing as a tool in a GitHub action is that the author of the GitHub action needs to pick a name that doesn’t collide with the names of tools that any consumers have installed. So I guess you should just pick a long unique name?
Can you use :deps in the alias to replace the deps?
Yeah, that might be an option, I’ll take a look