[Debian-med-packaging] Working on seqan (Was: r18848 - trunk/packages/seqan/trunk/debian)

Andreas Tille andreas at an3as.eu
Tue Feb 24 20:12:16 UTC 2015

Hi Michael,

On Tue, Feb 24, 2015 at 06:21:52PM +0000, Michael Crusoe wrote:
> > nice to see you working on this as well. :-)
> Whoops, this was an accidental commit. I'm used to having a local
> repository in Git land :-)

No problem - if it has lead to this clarification it was a lucky
> > While I agree that parallel builds could help in building seqan it was
> > the source of some errors in the past.  So we should take this change
> > with a grain of salt.
> Feel free to revert it.

Well, we simply should keep this in mind and revert it in case of
trouble.  As I said it could be of some profit and thus we could
> > Since I also had some pending changes which might support your attempt I
> > did some fine grained commits.  I did not minded about committing before
> > since the package does not build yet.  Please let me know if you want to
> > keep on working on seqan which would be really welcome.
> Sure, I'll help out. I'm friendly with the upstream team. Git would be
> great.

We have worked nicely together with upstream on previous versions but
even closer connection will be welcome for sure.  I remember that you
mentioned that you can drop the code copy in khmer for version 2.0 of
seqan - it would be cool if we could join the effort to approach this.
> > BTW, if you prefer Git I'm perfectly fine if you want to move the
> > repository to Git.  Usually the maintainer who does the actual work
> > decides and if we both are working on it and I'm neutral about the
> > VCS the decision is yours. ;-)
> >
> > Seme for prodigal where you commited as well.  If you prefer Git over
> > SVN we can move the repository.  Feel free to ping me about uploading
> > of prodigal.
> If you want, sure!

I'll put it on my short term todo list then.

> What is the procedure for new upstream versions?

As I said:  The person who does the actual work decides how this work is
done (=Do-O-cracy).  Seqan was introduced by Soeren Sonnenburg who at
some time lost interest.  Besides other roles I'm somehow also some kind
of garbage collector in those cases.  I'm not keen at all to do this so
if you feel obliged to seqan and you are using it (which I don't) feel
free to do whatever suits your needs (and I woll support this).  If you
might beet me in the SVN -> Git conversion that's perfectly fine (just
announce it here short before you are doing it to make sure our efforts
will not happen at the same time.)
Kind regards



More information about the Debian-med-packaging mailing list