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

Re: [MirageOS-devel] [ANN] mirage 3.2.0 released

  • To: Hannes Mehnert <hannes@xxxxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Mon, 24 Sep 2018 08:48:13 +0100
  • Cc: mirageos-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 24 Sep 2018 07:48:20 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=H3ktZiYgUsdG9hIR4dVrpF7 2ksYLsomigTTHMZzJ28OvukFFOncNAueXowC9cjnWusute3tKS/bwYd8yM2YddHl npHCYPWXLqTntKAfj/p3I599eq8hqgph3i1XRXLfLJ5Mro22x/6caOCY3W+P4U7P dWkQ7VgvB3l3i8AdprgM=
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

On 24 Sep 2018, at 08:42, Hannes Mehnert <hannes@xxxxxxxxxxx> wrote:

Several unneeded type aliases were removed:
 `netif` from Mirage_protocols.ETHIF
 `ethif` and `prefix` from Mirage_protocols.IP
 `ip` from Mirage_protocols.{UDP,TCP}
 `netif` and `'netif config` from Mirage_stack.V4
 `'netif stackv4_config` and `socket_stack_config` in Mirage_stack

All these changes were a lot of work to plumb through; thanks for
the hard work!

* which since a week switched to opam 2.0, and thus you'll only see
updates if you upgraded your opam to 2.0 (you can do so by following the
instructions on https://opam.ocaml.org/blog/opam-2-0-0/)

And this is an important point.  We need to decide when to stop
supporting opam1, since Mirage is of course rather dependent on
uptodate packages from the repository.

I'd suggest doing it sooner rather than later, since upstream opam 
has essentially frozen any non-stability updates to the 1.x branch.

In practical terms, that means we can:

- run `opam-package-upgrade` on local repositories in order to
  update their `opam` files to the 2.0 format. This will prevent 1.x
  from pinning them, but in return we can use the new rich metadata
  extensions in opam2.

- ensure all our CI runs on opam2 (which is mostly already done since
  the upstream ocaml-ci-scripts switched a few months ago).

Does anyone have a compelling reason to keep using opam1 at
this point?

MirageOS-devel mailing list



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