Re: Packaging Mauve and libClustalW
- To: Andreas Tille <email@example.com>, Debian Med Project List <firstname.lastname@example.org>
- Subject: Re: Packaging Mauve and libClustalW
- From: Aaron Darling <email@example.com>
- Date: Fri, 14 Mar 2008 16:37:46 +1000
- Message-id: <[🔎] 47DA1D3A.firstname.lastname@example.org>
- In-reply-to: <alpine.DEB.1.00.0803122255420.12942@wr-linux02>
- References: <alpine.DEB.1.00.0802140924260.4219@wr-linux02> <20080214142944.GF27364@kunpuu.plessy.org> <alpine.DEB.1.00.0803122255420.12942@wr-linux02>
Hi again Andreas,
Andreas Tille wrote:
Aaron, just for the sake of my private packaging: Do I understand
things right that your libMUSCLE is a replacement for libClustalW
and I might be able to drop libClustalW in favour of libMUSCLE?
My plan is to work on Mauve Debian packages in my private repository
until the issues above will be solved nicely.
Yes, libMUSCLE and libClustalW provide redundant functionality from
Mauve's point of view. The libMems codebase had been relying on
clustalw for a few functions, and as of today I have removed those
dependencies and updated libMems and mauveAligner accordingly. It
should now be possible to build everything without libClustalW.