[ocaml-platform] Dev Version as Package?

[Malcolm Matalka]

Each project I have has its own opam repo which I put as higher priority
to the basic one.  Does this do what you want?

Trevor Smith <trevorsummerssmith at gmail.com> writes:

> 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
> Platform at lists.ocaml.org
> http://lists.ocaml.org/listinfo/platform