unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add Ribotaper.
Date: Thu, 7 Jul 2016 15:45:05 +0200	[thread overview]
Message-ID: <idjwpkxtvdq.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <577E59D2.3010107@uq.edu.au>


Ben Woodcroft <b.woodcroft@uq.edu.au> writes:

> On 07/07/16 19:26, Ricardo Wurmus wrote:
>> Hi Guix,
>>
>> this patch adds a bioinformatics tool called "Ribotaper".  It needs a somewhat
>> older version of bedtools, because the output format produced by bedtools
>> changed after version 2.18.0 (they don't seem to care about semantic
>> versioning).  This is why this patch not only adds a variable "ribotaper" but
>> also "bedtools-for-ribotaper".
>>
>> Do you think I should rather name it "bedtools-2.18" and make it public so
>> that users can install it?
>
> This would be my preference, IIUC this is the current way we do this. Is 
> there any difference from previous times we've had to include outdated 
> packages?

I actually prefer to just offer “bedtools-2.18” without restricting it
to just ribotaper, but we’d have to ensure that this version stays
around (adding a comment on top should be enough).

We currently have “guile-for-guile-emacs”, which offers a variant of
Guile, but the situation is slightly different here.  We also have
“armadillo-for-rcpparmadillo”.  In both cases, the packages are not
private.  In the former case the package name differs, but in the case
of armadillo it’s only the variable name that indicates that this is
special.

I think in the ribotaper/bedtools case we should just name the variable
“bedtools-2.18”  and make it public.

> Note that I just updated bedtools, although I imagine that won't help here.

No, the format hasn’t changed back.  Ribotaper was not developed with
the more recent versions, which all output more columns.

~~ Ricardo

  reply	other threads:[~2016-07-07 13:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07  9:26 [PATCH] Add Ribotaper Ricardo Wurmus
2016-07-07  9:26 ` [PATCH] gnu: " Ricardo Wurmus
2016-07-07 13:32 ` [PATCH] " Ben Woodcroft
2016-07-07 13:45   ` Ricardo Wurmus [this message]
2016-07-08 22:52     ` Ben Woodcroft
2016-07-09 19:43       ` Ricardo Wurmus
2016-07-10 11:30         ` Ben Woodcroft

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=idjwpkxtvdq.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=b.woodcroft@uq.edu.au \
    --cc=guix-devel@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).