<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">It looks like these are all heading in roughly the same direction. Richard Mortier has been cleaning up the Mirage Vagrant image (which in turn uses OCaml and OPAM), and it has a slightly more sophisticated networking setup.<div class=""><br class=""></div><div class=""><a href="https://github.com/mirage/mirage-vagrant-vms" class="">https://github.com/mirage/mirage-vagrant-vms</a><br class=""><div class=""><br class=""></div><div class="">I'll look into the Vagrant registry once the Mirage one settles down a bit.</div><div class=""><br class=""></div><div class="">-anil</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 29 Nov 2014, at 15:16, Nate Foster <<a href="mailto:jnfoster@cs.cornell.edu" class="">jnfoster@cs.cornell.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">+1 to Vagrant. It makes VM construction and distribution really simple. And it makes it easy for all of us to share resources that go into VMs without having to ship GBs of opaque images around.<div class=""><br class=""></div><div class="">Ben Greenman has already supplied a pointer to the Cornell CS 3110 Vagrant scripts:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/cs3110/vagrant-opam" target="_blank" class="">https://github.com/cs3110/vagrant-opam</a><br class=""></div><div class=""><br class=""></div><div class="">Speaking just for myself, I'd be very happy if this stayed roughly in sync with Anil's efforts.</div><div class=""><br class=""></div><div class="">-N</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Nov 28, 2014 at 5:27 AM, Anil Madhavapeddy <span dir="ltr" class=""><<a href="mailto:anil@recoil.org" target="_blank" class="">anil@recoil.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I thought it might be useful to split out the discussion on specific technologies. Vagrant has come up several times, and it provides a useful mechanism to centralise not only the compiler distribution, but also editor tools and support infrastructure.<br class="">
<br class="">
We'd like to provide a Vagrant distribution for our upcoming FP course in Cambridge next term [1]. We already have a Vagrant VM that combines OCaml with the MirageOS here:<br class="">
<br class="">
<a href="https://github.com/mirage/mirage-vagrant-vms" target="_blank" class="">https://github.com/mirage/mirage-vagrant-vms</a><br class="">
<br class="">
I'm planning to split it out to make an OCaml-only base image. If anyone has similar Vagrant setups that incorporate editor support and so on, I'd appreciate a pointer. We're going to license our scripts under the CC0 public domain to make them as easily cut-and-pastable as possible.<br class="">
<br class="">
There's a 'Vagrant Cloud' in beta that can host pointers to such images, and we're happy to host binary blobs, under a central 'ocaml' organisation if that's available.<br class="">
<br class="">
[1] <a href="https://www.cl.cam.ac.uk/teaching/1415/L28/" target="_blank" class="">https://www.cl.cam.ac.uk/teaching/1415/L28/</a><br class="">
<br class="">
thanks<br class="">
Anil<br class="">
<br class="">
_______________________________________________<br class="">
Teaching mailing list<br class="">
<a href="mailto:Teaching@lists.ocaml.org" class="">Teaching@lists.ocaml.org</a><br class="">
<a href="http://lists.ocaml.org/listinfo/teaching" target="_blank" class="">http://lists.ocaml.org/listinfo/teaching</a><br class="">
</blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></div></body></html>