From: nafkhamdc <navid.afkhami@mdc-berlin.de>
To: 68371@debbugs.gnu.org
Cc: nafkhamdc <navid.afkhami@mdc-berlin.de>
Subject: [bug#68371] [PATCH] gnu: Add r-jaspar2020.
Date: Wed, 10 Jan 2024 14:22:37 +0000 [thread overview]
Message-ID: <c61c85dc59f58ea507efe7016c59d2efface5b37.1704896557.git.navid.afkhami@mdc-berlin.de> (raw)
* gnu/packages/bioconductor.scm (r-jaspar2020): New variable.
Change-Id: I84f0fc2a7defc5d179ffc24aa1f30177cb3b3060
---
gnu/packages/bioconductor.scm | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/gnu/packages/bioconductor.scm b/gnu/packages/bioconductor.scm
index 7c4272f8be..e4021fe756 100644
--- a/gnu/packages/bioconductor.scm
+++ b/gnu/packages/bioconductor.scm
@@ -6003,6 +6003,27 @@ (define-public r-deconstructsigs
closely reconstructs the mutational profile.")
(license license:gpl2+)))
+(define-public r-jaspar2020
+ (package
+ (name "r-jaspar2020")
+ (version "0.99.10")
+ (source
+ (origin
+ (method url-fetch)
+ (uri (bioconductor-uri "JASPAR2020" version
+ 'annotation))
+ (sha256
+ (base32 "0nrp63z7q2ivv5h87f7inpp2qll2dfgj4227l4rbnzii38a2vfdr"))))
+ (properties `((upstream-name . "JASPAR2020")))
+ (build-system r-build-system)
+ (native-inputs (list r-knitr))
+ (home-page "https://jaspar.elixir.no/")
+ (synopsis "Data package for JASPAR database (version 2020)")
+ (description "Data package for JASPAR2020.
+To explore these databases, utilize the TFBSTools
+package (version 1.23.1 or higher).")
+ (license license:gpl2)))
+
;; This is a CRAN package, but it depends on Bioconductor packages.
(define-public r-jetset
(package
base-commit: 537768018ee03a6a9a5562022a16b47ac287d131
prerequisite-patch-id: 103e1e7922398cbadee6250d96974c6b8ca89fdb
--
2.34.1
next reply other threads:[~2024-01-10 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 14:22 nafkhamdc [this message]
2024-01-10 17:50 ` bug#68371: [PATCH] gnu: Add r-jaspar2020 Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c61c85dc59f58ea507efe7016c59d2efface5b37.1704896557.git.navid.afkhami@mdc-berlin.de \
--to=navid.afkhami@mdc-berlin.de \
--cc=68371@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.