From: Sebastian Gibb via Guix-patches via <guix-patches@gnu.org>
To: 65652@debbugs.gnu.org
Cc: Sebastian Gibb <mail@sebastiangibb.de>, rekado@elephly.net
Subject: [bug#65652] [PATCH] gnu: Add r-consort.
Date: Thu, 31 Aug 2023 10:42:15 +0200 [thread overview]
Message-ID: <f99478103e05500d7a431a6746264473f59bd18f.1693471330.git.mail@sebastiangibb.de> (raw)
* gnu/packages/consort.scm (r-consort): New variable.
---
gnu/packages/cran.scm | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/gnu/packages/cran.scm b/gnu/packages/cran.scm
index 4ec6b802ff..cccf02026e 100644
--- a/gnu/packages/cran.scm
+++ b/gnu/packages/cran.scm
@@ -343,6 +343,29 @@ (define-public r-chromomap
(license (list license:gpl3
license:isc)))) ;for bundled d3js
+(define-public r-consort
+ (package
+ (name "r-consort")
+ (version "1.2.0")
+ (source (origin
+ (method url-fetch)
+ (uri (cran-uri "consort" version))
+ (sha256
+ (base32
+ "1jshk53121w58i4if593qzxm6lcrrggz8parwhqvv6hnbx51rhck"))))
+ (properties `((upstream-name . "consort")))
+ (build-system r-build-system)
+ (native-inputs (list r-knitr))
+ (home-page "https://github.com/adayim/consort/")
+ (synopsis "Create Consort Diagram")
+ (description
+ "To make it easy to create CONSORT diagrams for the transparent reporting of
+participant allocation in randomized, controlled clinical trials. This is done
+by creating a standardized disposition data, and using this data as the source
+for the creation a standard CONSORT diagram. Human effort by supplying text
+labels on the node can also be achieved.")
+ (license license:expat)))
+
(define-public r-collections
(package
(name "r-collections")
base-commit: d6966b8a5b4f2ddda2bc685b9642e7a1c2cbe17c
--
2.39.2
next reply other threads:[~2023-08-31 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 8:42 Sebastian Gibb via Guix-patches via [this message]
2023-10-30 11:30 ` bug#65652: [PATCH] gnu: Add r-consort Christopher Baines
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=f99478103e05500d7a431a6746264473f59bd18f.1693471330.git.mail@sebastiangibb.de \
--to=guix-patches@gnu.org \
--cc=65652@debbugs.gnu.org \
--cc=mail@sebastiangibb.de \
--cc=rekado@elephly.net \
/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).