[opam-devel] [ocaml-platform] OCamlot

Anil Madhavapeddy anil at recoil.org
Mon Sep 30 01:34:18 BST 2013

On 13 Feb 2013, at 22:42, Anil Madhavapeddy <avsm2 at cl.cam.ac.uk> wrote:

> On 13 Feb 2013, at 21:24, Mike Lin <mlin at mlin.net> wrote:
>> So therefore we build one from scratch!!??
> <snip>
>> I'd asked whether options like that were thoroughly considered before deciding to invent one here, and I'm sorry but I haven't gotten that impression so far. 
> Yeah, of course.  As with all these things, there's a combination of broad requirements ("does it build on X") with rather specialised ones ("I need to fork this OPAM chroot to build these 3 variants in independent copy-on-write trees").


I just wanted to update you on this thread:

I went back and looked at Travis again due to the pull request feature, and it's now really ideal for all the frontend requirements.  We're finding a happy compromise with doing the basic testing with Travis, and using it to fire off the more sophisticated tests using OCamlot on the backend.  All in all, very smooth stuff, and this is now live for OPAM.

The main difference with the scripts from your blog post is that I built a matrix of PPA packages for all the various versions of OCaml and OPAM, so it's less resource intensive for the Travis folk.

I wonder if it's worth proposing native OCaml/OPAM support within Travis itself, once OPAM 1.1  is released...


More information about the opam-devel mailing list