Re: 0install as an OCaml package manager
Thomas Leonard <[email protected]> Tue, 6 Dec 2016 18:01:19 +0000
| Newsgroups | gmane.comp.file-systems.zero-install.devel |
|---|---|
| Message-ID | <CAG4opy_gOy_MfxE8dPm-wWP6UmER7m03E_ANYHko0_5OTan+eQ@mail.gmail.com> |
On 5 December 2016 at 22:06, Yawar Amin <[email protected]> wrote: > Apologies if this has been discussed before, but it's rather hard to search > for. Has there been any thought given towards using 0install as an > alternative package manager to OPAM? If not, can anyone shed any light on > what it would take, at a minimum, to start with 0install and > ocamlc/ocamlbuild, and end up with OCaml package management? The main problem is that OCaml library binaries are only compatible with the exact versions of the libraries they are compiled against. e.g. if you compile cohttp 0.21.0 against uri 1.8.0 then the resulting cohttp binary isn't usable if you want to compile a program with cohttp 0.21.0 but with uri 1.9.0. So, you'd need to get 0compile to add extra constraints to the generated feeds. You also need to decide when to drop binaries from the cache. e.g. do you want to keep both cohttp-0.21.0+uri-1.8.0 and cohttp-0.21.0+uri-1.9.0? You can easily end up with a lot of combinations. opam only keeps one binary for each package, but that has its own problems. -- talex5 (GitHub/Twitter) http://roscidus.com/blog/ GPG: 5DD5 8D70 899C 454A 966D 6A51 7513 3C8F 94F6 E0CC GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi