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

a solution for packages on imports that got kicked out of CRAN #68

Open
LunaSare opened this issue Apr 29, 2020 · 2 comments
Open

a solution for packages on imports that got kicked out of CRAN #68

LunaSare opened this issue Apr 29, 2020 · 2 comments

Comments

@LunaSare
Copy link
Member

Packages on imports that are not on CRAN anymore, such as reports, or that were never on CRAN, such as phyloch but that we still need for datelife.

A potential solution here
https://www.r-bloggers.com/%F0%9F%93%A6-managing-dependencies-in-packages/

@bomeara
Copy link
Member

bomeara commented May 13, 2020

Or we could just get rid of those dependencies in some other way. Is reports needed? Does phyloch make things easier, or is it just one function with a system call that we could develop an analog to?

@LunaSare
Copy link
Member Author

I tried hosting the function from reports that we need, but it depends on so many other things from its package that it stopped making sense. The phyloch functions that we use are hosted on datelife in https://github.com/phylotastic/datelife/blob/master/R/pkg_phyloch_functions.R
With more packages dropping from cran, it made sense to try implementing the method described on the r-bloggers post to manage dependencies more efficiently.

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

No branches or pull requests

2 participants