opam-version: "2.0"
maintainer:   "Romain Calascibetta <romain.calascibetta@gmail.com>"
authors:      "Romain Calascibetta <romain.calascibetta@gmail.com>"
homepage:     "https://github.com/mirage/typebeat"
bug-reports:  "https://github.com/mirage/typebeat/issues"
dev-repo: "git+https://github.com/mirage/typebeat.git"
doc:          "https://mirage.github.io/typebeat/"
license:      "MIT"

build: [
  ["jbuilder" "subst" "-p" name] {pinned}
  ["jbuilder" "build" "-p" name "-j" jobs]
  ["jbuilder" "runtest" "-p" name "-j" jobs] {with-test}
]
depends: [
  "ocaml" {>= "4.03.0"}
  "jbuilder" {>= "1.0+beta9"}
  "angstrom" {>= "0.9.0" & < "0.14.0"}
  "alcotest" {with-test}
]
synopsis: "Agnostic parser of the `Content-Type` in OCaml"
description: """
[![Build Status](https://travis-ci.org/mirage/typebeat.svg?branch=master)](https://travis-ci.org/mirage/typebeat)

TypeBeat is a pure implementation of the parsing of the `Content-Type`'s value
(see [RFC822](https://tools.ietf.org/html/rfc822) and
[RFC2045](https://tools.ietf.org/html/rfc2045)). The reason of this *light*
library is to compute a complex rule. Indeed, it's __hard__ to parse the value
of the `Content-Type`, believe me.

So it's a common library if you want to know the value of the `Content-Type` and
don't worry, we respect the standard. We saved
the [IANA](https://www.iana.org/assignments/media-types/media-types.xhtml)
database too."""
url {
  src:
    "https://github.com/mirage/typebeat/releases/download/v0.3/typebeat-0.3.tbz"
  checksum: "md5=03d8badc8ca7e9d2794b4cd3093d6d0c"
}
