Hi all, I will see what I can do in this. Fixing up libzstd and seqan are next on my list of debian things to do. PhD stuff is still talking up nearly all of my time, but I'll do my best to have something reviewable by the end of the weekend.
Shall we start with a "simple" libseqan2-dev package with the latest upstream version (2.2.0)? I'll see if I can build on Michael's work in the seqan2 package. Cheers, K On 11:29 20/07, Michael Crusoe wrote: > Agreed > > On Wed, Jul 20, 2016 at 11:16 AM, Andreas Tille <[email protected]> wrote: > > > On Wed, Jul 20, 2016 at 10:57:44AM +0200, Michael Crusoe wrote: > > > Are the upstreams using 2.0, 2.1, or 2.2? > > > > Well, flexbar is using 2.1.1 - but if you ask me we should follow the > > latest seqan upstream and if needed adapt other packages. That's why I > > think we should be quick to have time for this transition. > > > > > We may need to package each separately.. > > > > Lets at least start with the latest and see what might be really needed. > > Currently we have no 2.x at all which is way worse than having at least > > the latest one. > > > > Agreed, but I have no time for the near future; sorry. > > > > > > 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 > [email protected] > +32 (0) 2 808 25 58 > +1 480 627 9108 --- Kevin Murray 0xA4B4EE6A
