Bug#754504: ITP: libpedantic-clojure -- Checkout dependency graphs for common unexpected cases
I have built a working package for version 0.2.0:
https://github.com/ehashman/pedantic
https://csclub.uwaterloo.ca/~ehashman/debian/libpedantic-clojure/
You can test it by installing the package and attempting an import in
the REPL:
$ clojure -cp /usr/share/java/pedantic.jar
Clojure 1.8.0
user=> (use 'pedantic.core)
nil
user=> (doc set-ranges!)
-------------------------
pedantic.core/set-ranges!
([ranges paths])
Set ranges to contain all paths that asks for a version range
You may note the dependency on libpomegranate-clojure version 0.2.0,
which I requested an upgrade for in #852246.
After chatting with Phil, I learned that when you build some project A
with leiningen, and project A depends on project B, and both projects
depend on different versions of project C (say C_A and C_B), then C_A,
the version required by A, will be used in the build.
Hence, there should be no problem with upgrading libpomegranate-clojure
to 0.3.1, as it's currently working and tested in the lein builds.
- e
Reply to: