[MirageOS-devel] require opam 1.2 in mirage?

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

A few reasons why we should probably require OPAM 1.2 in Mirage now:

- The development workflow is far nicer.

- In `is-mirage-broken`, there's an oddly non-deterministic failure where an 
older version of cohttp is sometimes installed (see 
https://github.com/mirage/is-mirage-broken/tree/master/logs and the 
mirage-skeleton failures).  OPAM 1.2 lets us specify `opam install cohttp>0.14` 
which will force the latest versions.

- OPAM 1.1 is in a broken state on Ubuntu 14.10, so we can segway people into 
using the PPA with OPAM 1.2 instead.

We do need a patch to test the OPAM version in the Mirage tool before doing 
this though.  

-a
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel