all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add hmmer
Date: Sun, 21 Jun 2015 20:11:31 +0200	[thread overview]
Message-ID: <20150621181131.GA17424@thebird.nl> (raw)
In-Reply-To: <87egl57zh0.fsf@netris.org>

On Sun, Jun 21, 2015 at 01:17:31PM -0400, Mark H Weaver wrote:
> It's not good that hmmer bundles its own copy of easel.  If we ever need
> easel for another package, we should find a way to build hmmer against
> the external easel library.  Having multiple copies of the same library
> on the system potentially means multiple copies in RAM, and more
> importantly: multiple copies that need to be patched for fixes,
> especially security fixes.

It is quite common in bioinformatics tools to include foreign code.
One reason in favour of including the original setup that is it is
THAT what the authors and others test and run. Bringing in our own
dependencies is bound to open a can of worms - there often is a reason
they bring in that packaged code. One reason is that they depend on an older
version ;). 

For that reason I favor deploying what the original authors suggest. I
am not too concerned about security fixes as long as the tools run in
user space and do not expose network services. Most bioinformatics
tools are in that category.

Pj.

  reply	other threads:[~2015-06-21 18:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21  8:52 [PATCH] gnu: Add hmmer Ben Woodcroft
2015-06-21  9:51 ` Ricardo Wurmus
2015-06-21 10:17   ` Ben Woodcroft
2015-06-21 17:17     ` Mark H Weaver
2015-06-21 18:11       ` Pjotr Prins [this message]
2015-06-21 18:23         ` Ricardo Wurmus
2015-06-24  1:37           ` Ben Woodcroft
2015-06-24  1:48             ` Ben Woodcroft
2015-06-24  1:52               ` Ben Woodcroft
2015-06-24  4:41                 ` Mark H Weaver

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=20150621181131.GA17424@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.