Hi opam-devel,
You may be interested in this document being elaborated by Edward Yang
as part of his work "cabal new-build" that is described as a
"nix-style local build" for cabal (a core Haskell tool that is on the
crossroad between opam and oasis and ocamlbuild, and as you could
guess has unsat
One aspect of the tool exhibited in this document that I found
interesting is that the design and user experience is not concentrated
on a "local root to develop a new package" workflow, but "local root
to develop a set of related packages together" workflow :
multi-package. There is a conceptual d
On Friday 2 September 2016 at 14:17, Gabriel Scherer wrote:
> To my knowledge there is no such established multi-package concept in
> related OCaml tooling these days, and there are cases where we don't
> do very well on this workflow.
Having a switch shared by the packages you are developing eac