From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 0/4] Add sra-tools.
Date: Fri, 17 Apr 2015 14:42:40 +0200 [thread overview]
Message-ID: <87lhhr2af3.fsf@mango.localdomain> (raw)
In-Reply-To: <87383zdv9v.fsf@gnu.org>
Ludovic Courtès writes:
>> I had to remove libxml2 from the inputs to sra-tools, resulting in a
>> failure to build a couple of loader tools. The reason for this is that
>> I encountered linker problems like these:
>
> It looks like an upstream bug? And why is it being statically-linked
> anyway? It would be nice if they would default to dynamic linking,
> which is more efficient in terms of memory use, etc.
Indeed. I will file a bug report upstream.
>> + (synopsis "API for accessing Next Generation Sequencing data")
>
> I would put quotes around “Next Generation”. :-)
"Next-generation sequencing" is an actual term (although it sounds a
little silly). It refers to high-throughput sequencing technology.
See http://www.nature.com/subjects/next-generation-sequencing
>> + (synopsis "Java bindings for NGS SDK")
>> + (description
>> + (string-append (package-description ngs-sdk)
>> + "\n\nThis package contains the Java bindings."))))
>
> ‘description’ should be a string literal, otherwise xgettext won’t catch
> it, thereby preventing i18n.
>
> What I would do is just keep ‘description’ unchanged, or rewrite it.
> Keeping it unchanged is OK here since the synopsis makes it clear that
> these are Java bindings.
Okay, I'll just keep the inherited description then. I should note that
"python-wrapper" in python.scm also does not use a string literal.
~~ Ricardo
prev parent reply other threads:[~2015-04-17 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 12:54 [PATCH 0/4] Add sra-tools Ricardo Wurmus
2015-04-17 8:16 ` Ludovic Courtès
2015-04-17 12:42 ` Ricardo Wurmus [this message]
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=87lhhr2af3.fsf@mango.localdomain \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=ludo@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.