<p dir="ltr">I just pushed seqan2 (with 2.1.0) </p>
<br><div class="gmail_quote"><div dir="ltr">Mar, 16 feb. 2016, 22:41, Kevin Murray <<a href="mailto:kevin@kdmurray.id.au">kevin@kdmurray.id.au</a>> a scris:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all (mostly Michael and Andreas)<br>
<br>
Seqan 2.1.0 has been released today. I'd like to get a basic (documentation<br>
free) package of seqan released ASAP to experimental so that I can start<br>
packaging other things that require seqan 2 (and so I can use seqan and some of<br>
their applications myself).<br>
<br>
At the sprint we decided to split the package into two source packages:<br>
<br>
- seqan1: The previous 1.4.2 version of seqan. Builds:<br>
- seqan-dev: the 1.4.2 development headers only<br>
<br>
- seqan: The current (2.0.1 in git, soon to be 2.1.0) version of seqan. Builds:<br>
- libseqan2-dev: the 2.x headers<br>
- seqan-apps: misc applications not listed below<br>
- mason2: the Mason simulator<br>
- (at a later date) seqan-doc: the sphinx API documentation.<br>
- (at a later date) seqan-examples: the tutorials, cookbook and example/demo<br>
code<br>
<br>
I believe Michael started splitting out the seqan1.4 package. Could you advise<br>
us about your progress please?<br>
<br>
I will prepare the 2.1.0 libseqan2/apps packages this week (hopefully). The<br>
documentation packages will be a pain, and require packages that will be stuck<br>
in NEW for some time (and haven't even been uploaded yet).<br>
<br>
Cheers,<br>
K<br>
<br>
---<br>
Kevin Murray<br>
0xA4B4EE6A<br>
<br>
_______________________________________________<br>
Debian-med-packaging mailing list<br>
<a href="mailto:Debian-med-packaging@lists.alioth.debian.org" target="_blank">Debian-med-packaging@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging</a><br>
</blockquote></div><div dir="ltr">-- <br></div><div dir="ltr"><span style="color:rgb(34,34,34);font-family:'courier new',monospace;font-size:small;line-height:normal">Michael R. Crusoe CWL Community Engineer </span><a href="mailto:mcrusoe@msu.edu" target="_blank" style="color:rgb(17,85,204);font-family:'courier new',monospace;font-size:small;line-height:normal">crusoe@ucdavis.edu</a><br style="color:rgb(34,34,34);font-family:'courier new',monospace;font-size:small;line-height:normal"><span style="color:rgb(34,34,34);font-family:'courier new',monospace;font-size:small;line-height:normal">Common Workflow Language project University of California, Davis</span><br style="color:rgb(34,34,34);font-family:'courier new',monospace;font-size:small;line-height:normal"><a href="https://impactstory.org/MichaelRCrusoe" target="_blank" style="color:rgb(17,85,204);font-family:'courier new',monospace;font-size:small;line-height:normal">https://impactstory.org/MichaelRCrusoe</a><font size="2" style="color:rgb(34,34,34);font-family:'courier new',monospace;font-size:small;line-height:normal"> <a href="http://twitter.com/biocrusoe" target="_blank" style="color:rgb(17,85,204)">http://twitter.com/biocrusoe</a></font><br></div>