<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class="">On Apr 16, 2016, at 5:28 AM, Daniel Bünzli <<a href="mailto:daniel.buenzli@erratique.ch" class="">daniel.buenzli@erratique.ch</a>> wrote:<br class=""><br class="">Le vendredi, 15 avril 2016 à 20:40, Bryce Glover a écrit :<br class=""><blockquote type="cite" class="">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 (<a href="https://github.com/ocaml/opam/issues/1950" class="">https://github.com/ocaml/opam/issues/1950</a>) before we start making it so that other package managers can interact with the OPAM repository?<br class=""></blockquote><br class="">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.<br class=""><br class="">Best,<br class=""><br class="">Daniel<br class=""></blockquote><br class=""><div class=""> Whoops, must have been reading too much into what you guys are discussing here! Going much farther than <i class="">that</i> would be another matter altogether…</div><br class=""><div class="">Apologies for the misunderstanding, <br class=""> Bryce Glover<br class=""> <a href="mailto:RandomDSdevel@gmail.com" class="">RandomDSdevel@gmail.com</a></div></body></html>