unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add freebayes.
Date: Thu, 10 Mar 2016 10:56:38 +0100	[thread overview]
Message-ID: <87r3fi64h5.fsf@gnu.org> (raw)
In-Reply-To: <20160309073158.GA24805@jasmine>


Leo Famulari writes:

> On Wed, Mar 09, 2016 at 07:53:20AM +0100, Pjotr Prins wrote:
>> On Tue, Mar 08, 2016 at 04:44:13PM +0100, Roel Janssen wrote:
>> > One of the problems with the patch is probably the bulk of dependencies
>> > dragged in (for example, vcflib).  They use specific versions so they
>> > are tied to this package (so that's why I cannot package them separately).
>> 
>> This approach is very common in bioinformatics and one way they fight
>> dependency hell. Not the best way, admittedly.
>> 
>> It may be worthwhile to package vcflib, for example, separately as
>> freebayes merely requires the header files to compile. The problem is
>> that that te current vcflib does not include the headers from a
>> default install, if I understand Roel correctly.  Ricardo, can you
>> advice on this? Should we add the headers in guix through a vcflib
>> installer?

I would like to propose the following:

- Separate the packages, and when needed, add specific versions of the
  packages.

  Instead of trying to package arbitrary Git commits, I will look into
  whether I can use release versions instead, without impacting the final
  FreeBayes binary.

- Use ,(package-source ...) to unpack the sources of the packages to
  satisfy the "submodules" structure of projects that use this.

This way we can separate the packages, which yields the programs that
are now hidden in submodule sources.  It also gives us more complete
package descriptions for them.  We don't have to heavily modify the
project setups that rely on submodules (just extract sources the way
we do now).

I am working on doing this for FreeBayes.  It should yield separate
packages for: vcflib, tabixpp, multichoose, smithwaterman, filevercmp
and fsom.

I want to find out whether I can make "intervaltree" a library, as it
is meant to be:
  https://github.com/ekg/intervaltree

WDYT?

Kind regards,
Roel Janssen

  reply	other threads:[~2016-03-10  9:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 15:44 [PATCH] gnu: Add freebayes Roel Janssen
2016-03-08 23:55 ` Leo Famulari
2016-03-09  6:44   ` Pjotr Prins
2016-03-09  6:53 ` Pjotr Prins
2016-03-09  7:31   ` Leo Famulari
2016-03-10  9:56     ` Roel Janssen [this message]
2016-03-09 10:17 ` Ricardo Wurmus
  -- strict thread matches above, loose matches on Subject: below --
2016-05-02  9:25 Rob Syme
2016-05-02 15:21 ` Ricardo Wurmus
2016-05-03  7:32   ` Rob Syme
2016-05-03  7:45     ` Roel Janssen
2016-05-03  7:52       ` Rob Syme
2016-05-03 12:34         ` Pjotr Prins

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=87r3fi64h5.fsf@gnu.org \
    --to=roel@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).