Fork me on GitHub
#tools-deps
<
2020-02-19
>
souenzzo10:02:20

From https://github.com/portkey-cloud/cfn-yaml/issues/1 How I supposed to import a project withtout a clear ArtifactID? Consider: I publish my/lib {:rev :v1} that requires cfn-yaml {:git/url "" :sha v1} Someone else import my/lib {:rev :v1} portkey-cloud/cfn-yaml {:git/url "" :sha v2} It will result in 2 times in classpath.

Alex Miller (Clojure team)13:02:25

To get comparisons, you need to use consistent ids

Alex Miller (Clojure team)13:02:13

This is admittedly challenging with git deps, and they work best with things like tools that are edges of a dependency graph

dominicm13:02:40

I generally strongly recommend a id in the readme

Alex Miller (Clojure team)13:02:27

Seems like a good practice

souenzzo15:02:10

Can I explicit this good practice in here? https://www.clojure.org/guides/deps_and_cli#_using_git_libraries Something like Is a good practice explicit a ID in documentation/README case ou pretend to distribute just via git deps.

Alex Miller (Clojure team)15:02:32

it kind of is with the advice of

github-yourname/time-lib

👍 4
👎 4
dominicm14:02:02

If repos were the canonical source of what id they represented, that would solve this. It would also make the deps.edn format very different.

Alex Miller (Clojure team)14:02:53

it would also break forking use cases etc

souenzzo15:02:10
replied to a thread:Seems like a good practice

Can I explicit this good practice in here? https://www.clojure.org/guides/deps_and_cli#_using_git_libraries Something like Is a good practice explicit a ID in documentation/README case ou pretend to distribute just via git deps.