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

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

  • To: mirageos-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Joe <joe@xxxxxxx>
  • Date: Tue, 25 Sep 2018 12:08:00 +0200
  • Authentication-results: mail.tyknet.dk; dkim=none
  • Delivery-date: Tue, 25 Sep 2018 10:08:23 +0000
  • Dkim-filter: OpenDKIM Filter v2.10.3 mail.tyknet.dk 6FD86C3E8C7
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

On 09/24/2018 09:48 AM, Anil Madhavapeddy wrote:
On 24 Sep 2018, at 08:42, Hannes Mehnert <hannes@xxxxxxxxxxx> wrote:

* 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.
> [..snip..]
> Does anyone have a compelling reason to keep using opam1 at
> this point?

I think it would be very nice if we waited until there is an actual release of opam2, and perhaps even a few weeks after that to give it time to spread to the various package manager and distributions.

I tried to write up my other arguments, but to be honest I just sounded like a bitter old conservative, so I won't.
I think my first one can stand on its own anyway. :-)


MirageOS-devel mailing list



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