From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] Add Piranha.
Date: Wed, 27 Apr 2016 14:30:19 +0200 [thread overview]
Message-ID: <87inz32q04.fsf@gnu.org> (raw)
In-Reply-To: <idj8u008nru.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Tue, 26 Apr 2016 16:09:41 +0200")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> From 8ebcd50666e13407d2b74907c9bc5e37ee420192 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
> Date: Tue, 26 Apr 2016 16:08:47 +0200
> Subject: [PATCH] gnu: Add Piranha.
>
> * gnu/packages/bioinformatics.scm (piranha): New variable.
[...]
> + (add-after 'unpack 'copy-smithlab-cpp
> + (lambda* (#:key inputs #:allow-other-keys)
> + (mkdir "src/smithlab_cpp")
> + (for-each (lambda (file)
> + (copy-file file
> + (string-append "./src/smithlab_cpp/"
> + (basename file))))
Rather:
(install-file file "src/smithlab_cpp")
> + ,(origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/smithlabcode/smithlab_cpp.git")
> + (commit "3723e2d")))
> + (file-name "smithlab_cpp-3723e2d-checkout")
Either remove the commit ID from ‘file-name’ or introduce a ‘commit’
variable to avoid repetition.
> + (home-page "https://github.com/smithlabcode/piranha")
> + (synopsis "Peak-caller for CLIP-seq and RIP-seq data")
> + (description
> + "Piranha is a peak-caller for CLIP-seq and RIP-seq data.")
Could you expound a bit (info "(guix) Synopses and Descriptions")? :-)
OK with these changes.
Thanks!
Ludo’.
next prev parent reply other threads:[~2016-04-27 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 14:09 [PATCH] Add Piranha Ricardo Wurmus
2016-04-27 12:30 ` Ludovic Courtès [this message]
2016-05-19 9:27 ` 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=87inz32q04.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.