unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: [PATCH 08/10] gnu: Add ocaml-ppx-inline-test.
Date: Tue, 31 Jan 2017 21:58:13 +0100	[thread overview]
Message-ID: <20170131205815.14576-9-julien@lepiller.eu> (raw)
In-Reply-To: <20170131205815.14576-1-julien@lepiller.eu>

* gnu/packages/ocaml.scm (ocaml-ppx-inline-test): New variable.
---
 gnu/packages/ocaml.scm | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/gnu/packages/ocaml.scm b/gnu/packages/ocaml.scm
index 57a7fe6fc..b44966248 100644
--- a/gnu/packages/ocaml.scm
+++ b/gnu/packages/ocaml.scm
@@ -2210,3 +2210,24 @@ code based on type definitions, and a set of useful plugins for common tasks.")
     (description "The type_conv library factors out functionality needed by
 different preprocessors that generate code from type specifications.")
     (license license:asl2.0)))
+
+(define-public ocaml-ppx-inline-test
+  (package
+    (name "ocaml-ppx-inline-test")
+    (version "113.33.03")
+    (source (janestreet-origin "ppx_inline_test" version
+              "0859ni43fl39dd5g6cxfhq0prxmx59bd2bfq8jafp593ba4q0icq"))
+    (build-system ocaml-build-system)
+    (native-inputs
+     `(("js-build-tools" ,ocaml-js-build-tools)
+       ("opam" ,opam)
+       ("ppx-core" ,ocaml-ppx-core)))
+    (propagated-inputs
+      `(("ppx-driver" ,ocaml-ppx-driver)
+        ("ppx-tools" ,ocaml-ppx-tools)
+        ("ppx-core" ,ocaml-ppx-core)))
+    (arguments janestreet-arguments)
+    (home-page "https://github.com/janestreet/ppx_inline_test/")
+    (synopsis "Syntax extension for writing in-line tests in ocaml code")
+    (description "Syntax extension for writing in-line tests in ocaml code.")
+    (license license:asl2.0)))
-- 
2.11.0

  parent reply	other threads:[~2017-01-31 20:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 20:58 [PATCH 00/10] ocaml patches Julien Lepiller
2017-01-31 20:58 ` [PATCH 01/10] gnu: Add ocaml-fieldslib Julien Lepiller
2017-01-31 20:58 ` [PATCH 02/10] gnu: Add ocaml-ppx-core Julien Lepiller
2017-01-31 20:58 ` [PATCH 03/10] gnu: Add ocaml-ppx-optcomp Julien Lepiller
2017-01-31 20:58 ` [PATCH 04/10] gnu: Add ocaml-ppx-driver Julien Lepiller
2017-02-08 11:17   ` Ludovic Courtès
2017-02-13 21:22     ` Julien Lepiller
2017-02-14  9:12       ` Ludovic Courtès
2017-01-31 20:58 ` [PATCH 05/10] gnu: Add ocaml-cppo Julien Lepiller
2017-01-31 20:58 ` [PATCH 06/10] gnu: Add ocaml-ppx-deriving Julien Lepiller
2017-01-31 20:58 ` [PATCH 07/10] gnu: Add ocaml-ppx-type-conv Julien Lepiller
2017-01-31 20:58 ` Julien Lepiller [this message]
2017-01-31 20:58 ` [PATCH 09/10] gnu: Add ocaml-ppx-bench Julien Lepiller
2017-01-31 20:58 ` [PATCH 10/10] gnu: Add ocaml-ppx-compare Julien Lepiller
2017-02-07 20:16 ` [PATCH 00/10] ocaml patches Julien Lepiller
2017-02-07 22:24   ` Ben Woodcroft
2017-02-08 11:21     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170131205815.14576-9-julien@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).