From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add vcflib.
Date: Wed, 20 Apr 2016 15:06:09 +0200 [thread overview]
Message-ID: <idjpotka0qm.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <878u1aa62m.fsf@gnu.org>
Roel Janssen <roel@gnu.org> writes:
> From c934cee6c84a39de36ecb4c3a85340ff025b1343 Mon Sep 17 00:00:00 2001
> From: Roel Janssen <roel@gnu.org>
> Date: Tue, 22 Mar 2016 15:50:12 +0100
> Subject: [PATCH 6/8] gnu: Add fastahack.
> * gnu/packages/bioinformatics.scm (fastahack): New variable.
> ---
> gnu/packages/bioinformatics.scm | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
> diff --git a/gnu/packages/bioinformatics.scm b/gnu/packages/bioinformatics.scm
> index 261660f..9cbde46 100644
> --- a/gnu/packages/bioinformatics.scm
> +++ b/gnu/packages/bioinformatics.scm
> @@ -4951,3 +4951,37 @@ combinatorial configurations.\" G Ehrlich - Journal of the ACM (JACM),
> (description "A program to compare version strings. It intends to be a
> replacement for strverscmp.")
> (license license:gpl3+))))
> +
> +(define-public fastahack
> + (let ((commit "c68cebb4f2e5d5d2b70cf08fbdf1944e9ab2c2dd"))
> + (package
> + (name "fastahack")
> + (version (string-append "0-1." (string-take commit 7)))
> + (source (origin
> + (method url-fetch)
> + (uri (string-append "https://github.com/ekg/fastahack/archive/"
> + commit ".tar.gz"))
> + (file-name (string-append name "-" version
> "-checkout.tar.gz"))
I don’t think we should add “checkout” here.
> + (sha256
> + (base32 "0j25lcl3jk1kls66zzxjfyq5ir6sfcvqrdwfcva61y3ajc9ssay2"))))
> + (build-system gnu-build-system)
> + (arguments
> + `(#:tests? #f ; There are no tests to run.
> + #:phases
> + (modify-phases %standard-phases
> + (delete 'configure) ; There is no configure phase.
> + (replace 'install
> + (lambda* (#:key outputs #:allow-other-keys)
> + (let ((bin (string-append (assoc-ref outputs "out") "/bin")))
> + (install-file "fastahack" bin)))))))
> + (home-page "https://github.com/ekg/fastahack")
> + (synopsis "Program for indexing and sequence extraction from
> FASTA files")
This sounds a bit off. It’s “indexing of ... FASTA files” (not “from”)
but “sequence extraction from FASTA files”. Maybe dropping “Program
for” would help here:
“Index and extract sequences from FASTA files”
What do you think?
> + (description "Fastahack is a small application for indexing and extracting
> +sequences and subsequences from FASTA files. The included Fasta.cpp library
> +provides a FASTA reader and indexer that can be embeddedinto applications which
> +would benefit from directly reading subsequences from FASTA files. The library
> +automatically handles index file generation and use.")
“embeddedinto” should be split.
I would drop mention of “Fasta.cpp” – or is this really the name of the library?
> + ;; libdisorder is licensed GPLv2. The parent project (vcflib), of which
> + ;; this program is a submodule, is licensed MIT, which is the same as
> + ;; the Expat license.
> + (license (list license:gpl2 license:expat)))))
As before we use the license of this code and ignore the parent
project’s license.
Here’s a license problem, though. The files “Fasta.h” and “Fasta.cpp”
contain notices like this:
> // ***************************************************************************
> // FastaIndex.h (c) 2010 Erik Garrison <erik.garrison@bc.edu>
> // Marth Lab, Department of Biology, Boston College
> // All rights reserved.
> // ---------------------------------------------------------------------------
> // Last modified: 5 February 2010 (EG)
> // ---------------------------------------------------------------------------
“disorder.c” has license GPLv2+.
There’s a bug report mentioning this problem here:
https://github.com/ekg/fastahack/issues/8
As it is now we cannot include this in Guix upstream unless the non-free
files are removed in a snippet.
~~ Ricardo
next prev parent reply other threads:[~2016-04-20 13:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 15:24 [PATCH] Add vcflib Roel Janssen
2016-03-23 13:49 ` Ricardo Wurmus
2016-04-20 12:39 ` Roel Janssen
2016-04-20 12:46 ` Ricardo Wurmus
2016-04-22 7:24 ` Roel Janssen
2016-04-26 14:47 ` Ricardo Wurmus
2016-04-26 17:31 ` Roel Janssen
2017-01-16 21:59 ` Ricardo Wurmus
2016-04-20 12:49 ` Ricardo Wurmus
2016-04-26 21:50 ` Roel Janssen
2017-01-16 22:04 ` Ricardo Wurmus
2016-04-20 12:53 ` Ricardo Wurmus
2016-04-22 7:40 ` Roel Janssen
2016-04-26 14:47 ` Ricardo Wurmus
2016-04-26 17:37 ` Roel Janssen
2017-01-16 21:56 ` Ricardo Wurmus
2016-04-20 12:56 ` Ricardo Wurmus
2016-04-20 12:58 ` Ricardo Wurmus
2016-04-22 8:04 ` Roel Janssen
2016-04-22 11:27 ` Ricardo Wurmus
2016-04-25 9:20 ` Roel Janssen
2016-04-26 14:42 ` Ricardo Wurmus
2016-04-20 13:06 ` Ricardo Wurmus [this message]
2016-04-20 13:08 ` Ricardo Wurmus
2016-04-26 17:50 ` Roel Janssen
2016-04-26 17:51 ` Roel Janssen
2017-01-16 21:54 ` Ricardo Wurmus
2017-01-17 21:57 ` Roel Janssen
2017-01-18 8:24 ` Ricardo Wurmus
2016-04-20 13:18 ` 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
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=idjpotka0qm.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=roel@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).