<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I think you'll get into complex binary distribution when you distribute set of libraries which depends on system libraries. When you simply distribute binaries or if everything is statically linked that's much easier and opam should just work today (just need to be careful with architecture constraints). But would be interested to see if someone actually manage to do this properly :p<div class=""><br class=""></div><div class="">Thomas<br class=""><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 22 Jan 2016, at 13:34, Gabriel Scherer <<a href="mailto:gabriel.scherer@gmail.com" class="">gabriel.scherer@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">I would be interested in some more information on this. This seems very simple as you say it, but I had not thought about the fact that OPAM already has the capacities to act as a binary distribution platform -- I somehow thought that there would be an announcement of some new extra features at some point designed for binary distribution.<br class=""><br class=""></div>Louis, you are saying that this is feasible. Are you aware of this actually having been done? For example, is anyone working on providing a, say, opam repository for x86-64 binaries corresponding to the packages available on opam-repository?<br class=""><br class=""></div>I suppose that if people proposed that, they would probably pre-build binaries for only a subset of the possible packages or configurations. Would it work to mix a "binary repository" that provides only a subset of the packages, and the official source repository, and would package query solvers have a way to do the right thing there? Or would it be the responsibility of the alternate repository provider to include a source-only fallback for the non-distributed packages? (This would make it harder to have a single repository with binary packages for several architectures.)<br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Jan 22, 2016 at 7:37 AM, Louis Gesbert <span dir="ltr" class=""><<a href="mailto:louis.gesbert@ocamlpro.com" target="_blank" class="">louis.gesbert@ocamlpro.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The package/compiler descriptions fetch an archive and run custom commands for<br class="">
build and install, so although the standard repo only provides source<br class="">
packages, you are free to build from source or just download and install a<br class="">
precompiled binary: Opam itself is agnostic in that regard.<br class="">
<br class="">
Hope this helps,<br class="">
Louis Gesbert - OCamlPro<br class="">
<div class=""><div class="h5"><br class="">
Le jeudi 21 janvier 2016, 09:42:45 Edgar Aroutiounian a écrit :<br class="">
> Greetings all,<br class="">
><br class="">
> I’m trying to wrap up a compiler for opam, specifically this one<br class="">
><br class="">
> <a href="http://psellos.com/ocaml/compile-to-iphone.html" rel="noreferrer" target="_blank" class="">http://psellos.com/ocaml/compile-to-iphone.html</a><br class="">
> <<a href="http://psellos.com/ocaml/compile-to-iphone.html" rel="noreferrer" target="_blank" class="">http://psellos.com/ocaml/compile-to-iphone.html</a>><br class="">
><br class="">
> Its an ocaml compiler ready for iOS. Right now I have the repo here,<br class="">
><br class="">
> <a href="https://github.com/fxfactorial/opam-ios" rel="noreferrer" target="_blank" class="">https://github.com/fxfactorial/opam-ios</a><br class="">
> <<a href="https://github.com/fxfactorial/opam-ios" rel="noreferrer" target="_blank" class="">https://github.com/fxfactorial/opam-ios</a>><br class="">
><br class="">
> and its essentially in the same vein as:<br class="">
><br class="">
> <a href="https://github.com/whitequark/opam-android" rel="noreferrer" target="_blank" class="">https://github.com/whitequark/opam-android</a><br class="">
> <<a href="https://github.com/whitequark/opam-android" rel="noreferrer" target="_blank" class="">https://github.com/whitequark/opam-android</a>><br class="">
><br class="">
> but I very much would like to avoid having to do though the process of<br class="">
> building etc. Does opam not have to just be given a binary? This would make<br class="">
> it much easier methinks.<br class="">
><br class="">
> -Edgar Aroutiounian<br class="">
</div></div>_______________________________________________<br class="">
opam-devel mailing list<br class="">
<a href="mailto:opam-devel@lists.ocaml.org" class="">opam-devel@lists.ocaml.org</a><br class="">
<a href="http://lists.ocaml.org/listinfo/opam-devel" rel="noreferrer" target="_blank" class="">http://lists.ocaml.org/listinfo/opam-devel</a><br class="">
</blockquote></div><br class=""></div>
_______________________________________________<br class="">opam-devel mailing list<br class=""><a href="mailto:opam-devel@lists.ocaml.org" class="">opam-devel@lists.ocaml.org</a><br class="">http://lists.ocaml.org/listinfo/opam-devel<br class=""></div></blockquote></div><br class=""></div></div></body></html>