> Has anyone else encountered this situation before? Yes, and I also would be interested in a good solution. One idea we had was to share switch configurations. I'd like to say here's a whole switch: it has this name, these remotes (if remotes were switch specific), these pins, etc. Then, I want to share this config with my team, and declare that a build machine should switch to this particular config. I have no idea how to do this though, other than hacking some shell script.
On Tue, May 5, 2015 at 2:58 PM, Trevor Smith <[email protected]> wrote: > Hi all, > > We're using opam internally at work. I have two use cases for our internal > libraries: > > 1) "dev dependencies" -- I want what is in the repo. > 2) "explicit dependency" -- I want a given version. > > opam has #2 covered. > > However it is not clear to me how to do #1 correctly. I can, on a given > machine (ie not on an opam repository), pin a given package to a git repo. > But locally pinning isn't what I want. I want a package in an opam > repository to say "I depend upon this other dev package" so that our build > boxes, and various developer machines will all do the same thing, and I > don't need to separately pin everything on each box. > > Has anyone else encountered this situation before? > > Thoughts? Thanks. > > Trevor > > _______________________________________________ > Platform mailing list > [email protected] > http://lists.ocaml.org/listinfo/platform > >
_______________________________________________ Platform mailing list [email protected] http://lists.ocaml.org/listinfo/platform
