Thomas Gazagnaire
Thomas Gazagnaire
Right now, the target names are ocamlliifed: ``` $ cat tutorial/hello-key/dune.build (rule (target hello_key) (enabled_if (= %{context_name} "default")) (action (copy main.exe %{target}))) ``` This should be `hello-key` to match the...
This is currently the case if `config.ml` is at the root of the dune-workspace, as `build.config` contains: ``` (data_only_dirs universe) ... ``` But this is not true, if someone does...
It would be nice if the `app_info` device would contain more information, especially the target.
https://github.com/mirage/mirage/pull/1174 pick the last defined key -- maybe we want to merge these CLI options a bit more cleverly but it's unclear what's the best UX for this.
Sometimes you already know what device you want to mount and you don't need to generate a `make-fat*-image.sh`.
The current situation with buffers is a bit annoying. The various MirageOS (and other) libraries are using, at least: `strings`, `bytes`, `bigarrays` and `Cstruct.t`. Because of that, there are often...
The script should use `du -h -L` instead of `du -h`
The current support for disk images is not ideal. Crunch works great, but other backends (for instance `fat`) need some extra manual steps. Here a list of bugs: - [...
We should use `du -h -s .` to get only the summary.
New tentative for #1989