New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[meta] Tracking issue for Muen SK port #194

Closed
mato opened this Issue Jun 1, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@mato
Copy link
Member

mato commented Jun 1, 2017

From #190:

Next steps for integrating Muen support in Mirage:

  1. PR for the changes to mirage/ocaml-freestanding (@Kensan)
  2. An initial version of solo5-kernel-muen published to OPAM (@mato)
  3. A new version of ocaml-freestanding with the changes in (1) published to OPAM, adding | solo5-kernel-muen as a dependency (@mato)
  4. PR for the changes to mirage/mirage (@Kensan)
  5. (at some point after that) "Formal" releases of Solo5, Mirage with documentation for the Muen port.

@mato mato referenced this issue Aug 31, 2017

Closed

[tracking] Steps toward the Solo5 0.3.0 release #217

6 of 6 tasks complete
@mato

This comment has been minimized.

Copy link
Member Author

mato commented Feb 13, 2018

@Kensan I've published a solo5-kernel-muen to the Solo5/opam-solo5 repository. The next step is to get a PR adding the muen target to the mirage frontend. I presume you already have this ready somewhere?

We'll need to decide how to merge it, though technically it doesn't add any OPAM dependencies to mirage so I think it could go straight onto master, and I could add a development version of mirage to Solo5/opam-solo5.

@Kensan

This comment has been minimized.

Copy link
Contributor

Kensan commented Feb 24, 2018

I rebased the mirage commit and tested it with Solo5/solo5 and it seems to work fine. Let me know against which repos/branch I should submit a PR.

@mato

This comment has been minimized.

Copy link
Member Author

mato commented Mar 1, 2018

@Kensan I've now created a dev-solo5 branch for this and other upcoming Solo5-related changes: https://github.com/mirage/mirage/tree/dev-solo5, please open a PR against that.

@mato

This comment has been minimized.

Copy link
Member Author

mato commented Jun 1, 2018

This has been completed for some time, with the Mirage changes all in the dev-solo5 OPAM repository, so closing.

@mato mato closed this Jun 1, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment