I am wondering how difficult it would be to have the "git pin in opam file" feature without the fixpoint resolver. I think in many cases, the dependencies of package foo will be subsumed by the other dependencies listed in the opam file. If they are not, I would be happy to have the solver fail, telling me that this situation is too complicated for now. In that case, I would be happy either to come back to my shadow repository solution, or to inline the dependencies in my opam file.
On Wed, May 6, 2015 at 5:51 PM, Ashish Agarwal <[email protected]> wrote: > On Wed, May 6, 2015 at 4:51 AM, Thomas Braibant <[email protected] > > wrote: > > depends: [ >> "asn1-combinators" { = "0.1.1" } >> ... >> "foo" { git: "path-to-git/foo#bar"} >> ] >> > > This could be very useful. It would also help to allow {path: > $HOME/mycode}. With only git pins, developing multiple repos is still > difficult. You have to push the changes in one repo before testing them > with another repo. Sharing path pins would let multiple developers all work > on multiple repos, but each developer can still have fine control over > exactly what state each of the individual repos is at. The only slight > inconvenience is everyone has to standardize on the paths of their local > working directories, but that's not too bad as along as a $HOME variable > was allowed. > > >
_______________________________________________ Platform mailing list [email protected] http://lists.ocaml.org/listinfo/platform
