Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dep: install checkm and pplacer via conda #13

Closed
wants to merge 1 commit into from
Closed

dep: install checkm and pplacer via conda #13

wants to merge 1 commit into from

Conversation

thermokarst
Copy link
Contributor

No description provided.

@thermokarst
Copy link
Contributor Author

@misialq - this PR is a start for getting a pure-conda recipe in order. Unfortunately you'll have to sort out getting a functional pplacer build for macos. It looks like there has been a bit of churn on this topic over at bioconda/bioconda-recipes.

@ebolyen
Copy link
Contributor

ebolyen commented Jun 23, 2022

Yeah it also looks like very few have even attempted a source build, which is actually pretty odd for bioconda. I'm going to see if I can get such a recipe to work, and then a lot of that mess ought to be solved.

@misialq
Copy link
Contributor

misialq commented Jun 23, 2022

Thanks for looking into that @thermokarst and @ebolyen! 🙇

@ebolyen
Copy link
Contributor

ebolyen commented Jun 23, 2022

So some bad news:

I have half of a recipe that might work, except for a downstream dependency issue in pplacer itself.
pplacer has a dependency on sqlite3=1.6.3 (ocaml). OPAM used to know this as sqlite3-ocaml and around 2014 was probably the last time this version was publicly accessible. I could look into how opam repositories are handled, and then create a git clone of an ancient tag to create an artificial opam repository. This is already done for some other magical dependencies: https://github.com/matsen/pplacer-opam-repository/tree/master/packages

But I think the worse headline news is, this package cannot actually be compiled except by a handful of developers who happen to have this ancient version in their opam cache. Worse, we shouldn't expect any meaningful updates as pplacer is no longer developed or maintained.

I might be able to work around these things, but we'd be mocking out ancient versions of things to resuscitate a package that is already quite dead.
image


Does it make sense to go through that? Given the dependency on pplacer through CheckM, it seems like there may be a need for some kind of vsearch-style reimplementation of pplacer or maybe just a fork? Alternatively, it looks like there may be some alternatives: http://genesis-lib.org/ (although I can't tell at first glance if it's the same kind of problem, but it does mention RAxML-EPA as an alternative).

@ebolyen
Copy link
Contributor

ebolyen commented Jun 23, 2022

It looks like epa-ng might be a viable alternative, although that just pushes the issue up to CheckM.

@misialq
Copy link
Contributor

misialq commented Jun 24, 2022

Oh my, what a, pardon me, mess... 😭 Thanks for going through that @ebolyen! I discussed today with @nbokulich, and we both feel like this is way too much work for it to be worth it... We've had enough trouble with CheckM already (like python 3.8 compatibility issues, or the outdated DB) - let's not invest more effort into that. We are thinking that instead of doing that, we could put CheckM into its own, separate plugin which would not become part of the Library - that way we can keep those dependencies separate, install pplacer the way it is now being installed and be done with it. Instead we could invest time into integrating some more modern QC evaluation tools into moshpit (e.g. we have discussed BUSCO). What do you think?

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants