<p dir="ltr">Agreed that consistent names are good.</p>
<p dir="ltr">How about the following?</p>
<p dir="ltr">source package "seqan1" produces binary package "libseqan1-dev" (version 1.4.2) which provides and conflicts with "seqan-dev" for backwards compatibility. Existing reverse build-dependencies are updated to use the new name on a rolling basis.</p>
<p dir="ltr">source package "seqan2" produces binary package "libseqan2-dev", "seqan-apps", "libseqan2-docs" (version 2.1.x)</p>
<p dir="ltr">As for "mason2" that will be confusing given the current unrelated package "mason". </p>
<br><div class="gmail_quote"><div dir="ltr">Mie, 17 feb. 2016, 08:34, Andreas Tille <<a href="mailto:andreas@an3as.eu">andreas@an3as.eu</a>> a scris:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Wed, Feb 17, 2016 at 07:28:39AM +0000, Michael Crusoe wrote:<br>
> Yeah, I thought we had agreed to keeping the existing source package as<br>
> 'seqan' and make a new tree for version 2.x as 'seqan2' so we didn't have<br>
> to change any reverse build dependencies.<br>
<br>
I'm not against this agreement for the binaries but in this case we<br>
should also keep the name for the source package to keep source and<br>
binary names the same.<br>
<br>
On the other hand the number of dependencies is limited and a fresh<br>
upload of these should be easy. I do not mind what way you prefer but<br>
the way should be consistent in itself.<br>
<br>
Kind regards<br>
<br>
Andreas.<br>
<br>
> Mie, 17 feb. 2016, 08:23, Andreas Tille <<a href="mailto:andreas@an3as.eu" target="_blank">andreas@an3as.eu</a>> a scris:<br>
><br>
> > On Tue, Feb 16, 2016 at 01:40:43PM -0800, Kevin Murray wrote:<br>
> > > - seqan1: The previous 1.4.2 version of seqan. Builds:<br>
> > > - seqan-dev: the 1.4.2 development headers only<br>
> ><br>
> > Wait a moment:<br>
> ><br>
> > seqan*1* builds seqan**-dev<br>
> ><br>
> > > - seqan: The current (2.0.1 in git, soon to be 2.1.0) version of seqan.<br>
> > Builds:<br>
> > > - libseqan2-dev: the 2.x headers<br>
> ><br>
> > seqan** builds libseqan*2*-dev<br>
> ><br>
> > ? This does not sound sensible to me.<br>
> ><br>
> > > - seqan-apps: misc applications not listed below<br>
> > > - mason2: the Mason simulator<br>
> ><br>
> > ?? Again mason*2* - but we do not have any mason**<br>
> ><br>
> > > - (at a later date) seqan-doc: the sphinx API documentation.<br>
> > > - (at a later date) seqan-examples: the tutorials, cookbook and<br>
> > example/demo<br>
> > > code<br>
> ><br>
> > Please get the numbering straigt. I'd suggest to add '1' to any package<br>
> > that comes from source seqan1.<br>
> ><br>
> > Kind regards<br>
> ><br>
> > Andreas.<br>
> ><br>
> > --<br>
> > <a href="http://fam-tille.de" rel="noreferrer" target="_blank">http://fam-tille.de</a><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>
> ><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>
> ><br>
> --<br>
> Michael R. Crusoe CWL Community Engineer <a href="mailto:crusoe@ucdavis.edu" target="_blank">crusoe@ucdavis.edu</a><br>
> <<a href="mailto:mcrusoe@msu.edu" target="_blank">mcrusoe@msu.edu</a>><br>
> Common Workflow Language project University of California, Davis<br>
> <a href="https://impactstory.org/MichaelRCrusoe" rel="noreferrer" target="_blank">https://impactstory.org/MichaelRCrusoe</a> <a href="http://twitter.com/biocrusoe" rel="noreferrer" target="_blank">http://twitter.com/biocrusoe</a><br>
<br>
--<br>
<a href="http://fam-tille.de" rel="noreferrer" target="_blank">http://fam-tille.de</a><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>