[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[MirageOS-devel] 2.0 releases going into mirage-dev

  • To: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Mon, 3 Nov 2014 15:15:08 +0000
  • Delivery-date: Mon, 03 Nov 2014 15:15:26 +0000
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

I've started tagging all the libraries currently in mirage-dev and have 
uploaded releases of most of them to https://github.com/mirage/mirage-dev. 

Next steps:
- add constraints on packages that would conflict (mostly cohttp) in the main 
opam repo

- figure out why this ocaml-dns downgrade happens only on 4.02: 

Interesting question is what we do with mirage-dev now.  Should we instruct 
people to remove it?  It's actually more useful it seems to have remotes for a 
specific purpose (mirage/mirage-2-release) so that once they're done, they just 
contain archives.

If we bump mirage/mirage-dev to the git versions again, then users will always 
get the bleeding edge...


MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.