Re: Status of seqan

Cc: Kevin Murray <kevin@kdmurray.id.au>, Debian Med Project List <debian-med@lists.debian.org>, "Johannes T. Roehr" <johannes.roehr@fu-berlin.de>

Subject: Re: Status of seqan

From: Michael Crusoe <michael.crusoe@gmail.com>

Date: Wed, 20 Jul 2016 10:57:44 +0200

Message-id: <[🔎] CAD=WrcLPF+RmxcKLbbX8E6T3HYX62DLRk9owZzNjuJO+xbPLXQ@mail.gmail.com>

In-reply-to: <[🔎] 20160720085445.GD321@an3as.eu>

References: <20160122144528.GF8382@an3as.eu> <CAD=WrcKry8dsgnpR5Z22ye5ONdJpPqFx7yxNv0rjqqGCLf7bew@mail.gmail.com> <20160123093339.GB1458@latanatop> <[🔎] 20160720085445.GD321@an3as.eu>

Are the upstreams using 2.0, 2.1, or 2.2?

We may need to package each separately..

On Wed, Jul 20, 2016 at 10:54 AM, Andreas Tille <andreas@an3as.eu> wrote:

Hi folks,

upstreams are moving to seqan 2.x (I just received a mail from the
flexbar author). Could someone please give a status update. We
*really* need to move on. There are some monthes left until there wil
be a library transition freeze but seqan is heavy and I'm afraid we need
time.

So do we have any volunteers to continue this work?

Kind regards

Andreas.

--
http://fam-tille.de

Michael R. Crusoe
Community Engineer & Co-founder
Common Workflow Language project
https://impactstory.org/u/0000-0002-2961-9670
michael.crusoe@gmail.com
+32 (0) 2 808 25 58
+1 480 627 9108