On 04/16/2016 12:28, Daniel Bünzli wrote: > Le vendredi, 15 avril 2016 à 20:40, Bryce Glover a écrit : >> I’m just a lurker here, but I just couldn’t help but bring this up: >> shouldn’t we make OPAM installable system-wide per the original intent of >> issue #1950 (https://github.com/ocaml/opam/issues/1950) before we start >> making it so that other package managers can interact with the OPAM >> repository? > > The goal is not to make them *interact* with opam. AFAIR package managers are > not very keen on other tools fiddling with their prefixes. The goal is to > make it easy to transform OPAM packages into system packages > while retaining the ability to use the tooling (documentation tools, link > helpers, whathever) that allows to use them regardless if they are installed > via opam or not.
This sounds very useful, I'd be interested in trying this out when you have some (even pre-alpha) code ready. Would this make it possible to have an OCaml equivalent of gofed [1]? See: https://github.com/gofed/gofed#launching https://github.com/gofed/gofed#dependency-discovering https://github.com/gofed/gofed#check-of-up2date-dependencies-in-fedora Best regards, -- Edwin Török | Co-founder and Lead Developer Skylable open-source object storage: reliable, fast, secure http://www.skylable.com _______________________________________________ opam-devel mailing list opam-devel@lists.ocaml.org http://lists.ocaml.org/listinfo/opam-devel
