Anil Madhavapeddy
2016-12-08 12:29:15 UTC
[moving from infrastructure@ to ***@lists.ocaml.org]
Dear Ralf,
While you cannot specify dependencies directly in a dependency, you
can construct an OPAM remote that has `url` files that point directly
at the commit in question.
For example, https://github.com/mirage/mirage-dev has several such
instances with `url` files pointing to a specific fork or branch in git.
Your users will need to `opam repo add <name> <url>` of the OPAM
remote to pull in the new package descriptions.
regards,
Anil
Dear Ralf,
While you cannot specify dependencies directly in a dependency, you
can construct an OPAM remote that has `url` files that point directly
at the commit in question.
For example, https://github.com/mirage/mirage-dev has several such
instances with `url` files pointing to a specific fork or branch in git.
Your users will need to `opam repo add <name> <url>` of the OPAM
remote to pull in the new package descriptions.
regards,
Anil
Hi all,
I'm trying to use opam to express a highly volataile dependency, where
project B wants to say "I need exactly git commit X of project A".
Project A frequently has breaking changes, so just depending on "master"
("dev") is too coarse-grained. Currently, we have a submodule in
project B indicating the proper commit of project B, but with the
dependency graph getting larger than two nodes, this stops scaling, so
I'd like to use opam. I tried putting the git URL
("https://.../projectA.git#X") into the "depends" of project B, but
unfortunately that doesn't seem to be supported.
Is there another way to achieve a dependency on a particular git commit?
Kind regards,
Ralf
_______________________________________________
Infrastructure mailing list
http://lists.ocaml.org/listinfo/infrastructure
I'm trying to use opam to express a highly volataile dependency, where
project B wants to say "I need exactly git commit X of project A".
Project A frequently has breaking changes, so just depending on "master"
("dev") is too coarse-grained. Currently, we have a submodule in
project B indicating the proper commit of project B, but with the
dependency graph getting larger than two nodes, this stops scaling, so
I'd like to use opam. I tried putting the git URL
("https://.../projectA.git#X") into the "depends" of project B, but
unfortunately that doesn't seem to be supported.
Is there another way to achieve a dependency on a particular git commit?
Kind regards,
Ralf
_______________________________________________
Infrastructure mailing list
http://lists.ocaml.org/listinfo/infrastructure