[MirageOS-devel] What was the reasoning for splitting out mirage-http?

[Rudi Grinberg <rudi.grinberg@xxxxxxxxx>]

Hello,

Back in 2013, mirage-http was extracted out of cohttp into itâs own repository. Although Iâm ignorant of how the decision was made, I understand that there could have been good reasons for this a couple of years ago. Today, however, it seems like thereâs less good reasons for such a split. Now that opam supports multiple packages out of the same repo and since weâre planning on releasing cohttp backends as their own packages [1], maybe it makes sense to treat mirage-http the same way?

The reason why Iâm bringing this up now is that the current situation does have the disadvantage of confusing users and creating possibly unnecessary churn for maintainers [2]

Thanks,

Rudi.

[1] https://github.com/mirage/ocaml-cohttp/issues/238

[2] https://github.com/mirage/mirage/issues/301#issuecomment-90729110

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel