package mirage-fs

All checked builds pass
  1. Overview
  2. Docs
MirageOS signatures for filesystem devices

Install

dune-project
 Dependency

Authors

Maintainers

Sources

mirage-fs-v4.0.0.tbz
sha256=3d86761c23eec4ebf8154ec41f29ac6b5a08654eeaf134b3cd1be59e061d677b
sha512=d5ce102ae88771cf4a8198c37ba76e6d5ca0a87f4df76d6d7ad2a40c1161b3e731059234aea7fb3db997a9f16d84d8f75a34ff4a6e38765c2499278e5ba94567

Description

mirage-fs provides the [Mirage_fs.S][fs] signatures the MirageOS filesystem devices should implement.

Tags

org:mirage

Added to opam-repository:

README

mirage-fs — MirageOS signatures for filesystem devices

Build Status

mirage-fs provides the [Mirage_fs.S][fs] signature the MirageOS filesystem devices should implement.

Installation

mirage-fs can be installed with opam:

opam install mirage-fs

If you don't use opam consult the opam file for build instructions.

Documentation

The documentation and API reference is generated from the source interfaces. It can be consulted online or via odig doc mirage-fs.

License

mirage-fs is distributed under the ISC license, see the LICENSE.md file for its text.

Dependencies (6)

  1. mirage-kv >= "3.0.0" & < "5.0.0"
  2. cstruct >= "4.0.0"
  3. lwt >= "4.0.0"
  4. fmt
  5. dune
  6. ocaml >= "4.08.0"

Dev Dependencies

None

Optional Dependencies

None

Used by (2)

  1. docteur-unix < "0.0.3"
  2. fat-filesystem = "0.14.0"

Conflicts

None

Build status

Results of building mirage-fs with each compiler on check.ci.ocaml.org, run of against opam-repository 7cdc698. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
4.0.0 (this version) good good good good good
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure