Hello, It seems like I am a little bit stuck. I have found out that the mecat2[1] software has code duplicates and compiles fsa and ncbi-blast(+), both of which are already packaged. The first issue I have hit is that mecat2 uses ncbi-blast files interchangeably. That is, they have included (either some or all) of the ncbi-blast sources and are compiling the rest of the software with it, as well as using its headers (ncbi-blast+ doesn't seem to be a library, yet mecat2's upstream is directly using its headers and sources). It seems like upstream is only using these dependencies to build libhbn.a (searching sources.debian.org, I cannot find any other iterations of this library, so this library is very much original to mecat2). A simple grep we can get an idea of how extensively the ncbi_blast headers and soures are referenced: https://paste.debian.net/1154499/ Any help or suggestion would be much appreciated. Additionally, if this turns into a big work, then a helping hand with packaging this would also be much appreciated. Kind regards, Shayan Doust [1]: https://salsa.debian.org/med-team/mecat2/
Attachment:
0x6D7D441919D02395.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature