Welcome! Please see the About page for a little more info on how this works.

0 votes
in tools.deps.alpha by

I work on a project with 160+ deps that update frequently, and are all optional so don't belong in the project's deps.edn. An alias could work here, but the deps update frequently, so I'm left updating deps.edn (home or project level) more often than I'd like to.

One solution would be to support passing a path to a file to the {{clj}} command, e.g. {{clj -Sdepsf "path-to-file"}}. This way I could update that file without risking hosing my home or project deps.edn.

3 Answers

0 votes
by

Comment made by: alexmiller

What are you trying to do? Why do you have n config files?

0 votes
by

Comment made by: dchelimsky

This is really a development aid. When working on, for example, aws-api, I need access to any of the available services. Today, I'll start clj with the services I care about in {{-Sdeps}}, but it would be nicer to point to a deps.edn that has all an {{:all-services}} alias in it. This is one specific example, but I think you can imagine more. And yes, I realize I could add {{:all-services}} to either of ~/.clojure/deps.edn or the one in the project, but the convenience of composing across arbitrary files in addition to implicit files + {{-Sdeps}} would be, well, convenient.

Following on the aws-api example, users have asked for a means of requiring all services. We could satisfy that need with a tools.deps-formatted variant of https://github.com/cognitect-labs/aws-api/blob/master/latest-releases.edn.

0 votes
by
Reference: https://clojure.atlassian.net/browse/TDEPS-115 (reported by dchelimsky)
...