I'm very pleased to let you know that a minimal package universe for the
MirageOS 3 beta is available at
https://github.com/mirage/mirageos-3-beta . Instructions for trying it
out are in the README there. A summary of the changes in MirageOS 3 is
available at https://github.com/mirage/mirage/releases/tag/v3.0.0 , with
more detailed writeups forthcoming (and volunteers welcome!).
Please note that if you've added the
https://github.com/mirage/mirage-dev remote, you'll need to remove it to
get the package versions in the beta repository, as the versions noted
for packages in mirage-dev will always be higher than those in
mirageos-3-beta and thus preferred by the solver if opam knows about them.
What's expected to work:
- any library that's used to fulfill a request you make to the `mirage`
frontend tool via the `Mirage` module in your config.ml (like tls,
fat-filesystem, or mirage-net-solo5)
What probably won't work:
- other libraries that depend on or implement the module type
definitions in `mirage-types`, but aren't integrated into the `mirage`
frontend tool (like irmin, shared-block-ring, or 9p-protocol). If
you're a maintainer of such a library, have a look at
https://github.com/mirage/mirageos-3-beta/issues/1 for an explanation of
how to get a prerelease into the repository. PRs there are welcome :)
You may also find the `mirage-dev` branches of the `mirage-skeleton` and
`mirage-www` repositories to be of help in trying out MirageOS 3. See
https://github.com/mirage/mirage-skeleton/tree/mirage-dev and
https://github.com/mirage/mirage-www/tree/mirage-dev , respectively.
More documentation is coming, and the remaining TODOs for general
release are tracked at https://github.com/mirage/mirage/issues/592 .
Thanks,
Mindy
_______________________________________________
MirageOS-devel mailing list
[email protected]
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
