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. Best, Daniel _______________________________________________ opam-devel mailing list opam-devel@lists.ocaml.org http://lists.ocaml.org/listinfo/opam-devel
