On 24 Sep 2018, at 08:42, Hannes Mehnert <[email protected]> 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/
> <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?
regards,
Anil
_______________________________________________
MirageOS-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/mirageos-devel
