Hello, Ben Sturmfels <[email protected]> writes:
> Mathieu Lirzin <[email protected]> writes: > >> Hello Ben and Kristiyan, >> >> From a Clojure developer perspective, I think the most important >> thing >> is to ensure that the dependency resolution of Clojure Guix behave >> exactly the same as upstream. As a consequence I would be in favour >> of >> introducing dedicated maven-* package definitions matching the >> version >> included Clojure upstream. WDYT? > > Thanks Mathieu. To my naive understanding, this recommendation sounds > similar to what Kristiyan has done in the above debbugs#73432 patches > to > add "maven-3.8-core" etc. Could you elaborate a little please? My recommandation is similar to what Kristiyan has done. I am perfectly fine with the usage of maven-3.8-core as input to clojure-tools-deps package. However as you suggested I am in favour of depending on maven-resolver-1.8 instead of maven-resolver-1.6 because this is safer to depends on a minor version that matches what is distributed in the upstream clojure-tools bundle JAR. My point was to say that whenever the version of a tools.deps dependency involved in the dependency resolution algorithm evolves upstream, we should follow the version chosen upstream even if a slightly different version seems to work fine at first glance. I find it really important to ensure a consistent dependency resolution across systems in particular when working inside a team where not every is using Guix. > https://issues.guix.gnu.org/73432 This links helped me get all the history behind this patch. Thanks! -- Mathieu Lirzin
