HEADSUP: mirage-profile, ppx_cstruct

[Hannes Mehnert]

Dear everyone,

this is a headsup to let you know the package "mirage-profile" - which 
served for a good time to get traces in a xen shared ring for debugging 
unikernels, has been removed.

The background is that when we introduced solo5-xen-pvh support (since 
solo5 0.6.6, released 2020-07-21) - used by mirage 3.9.0 (2020-10-24), 
we no longer supported this tracing methodology.

As you can observe in https://ocaml.org/p/mirage-profile/latest, the 
mirage-profile package itself has been removed as dependency from all of 
our packages, and we just marked the mirage-profile repository as archived.


In the future, we expect to adapt OCaml 5 runtime tracing events for 
MirageOS unikernels - after we merge and release the OCaml 5 support for 
MirageOS :)


In a similar direction, the ppx_cstruct has been removed from a lot of 
core package. The reasoning is that ppx_cstruct has a huge dependency 
cone and generates a lot of code (in size and number of functions) - so 
we were able to enable warning 32 at more places :) This is as well a 
preparation for upcoming experimental changes (to use strings/bytes 
instead of bigarrays for allocations).

Please stay tuned, and if you encounter any issues and miss 
functionality, please open issues at the relevant repositories (if 
unclear where, just submit it at https://github.com/mirage/mirage).


All the best from the negative line count department (and stay tuned for 
upcoming code line removals),

Hannes