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

Control R package versioning #97

Open
lukejharmon opened this issue Dec 17, 2014 · 3 comments
Open

Control R package versioning #97

lukejharmon opened this issue Dec 17, 2014 · 3 comments
Assignees

Comments

@lukejharmon
Copy link
Member

R package updates can break Arbor functionality. We should maintain strict control over which versions we are loading, and allow someone to approve updates only when we know they work.

@jeffbaumes
Copy link
Member

+1. According to

http://stackoverflow.com/questions/17082341/installing-older-version-r-package

the answer is to point to specific source tarballs for each install - seems there is not a simple version argument in install.packages. Looks like the answer to this is to track down all those URLs and change Ansible to use them. We should also do this when testing things in Travis.

Jeff

@lukejharmon
Copy link
Member Author

Another option: http://rstudio.github.io/packrat/

@jeffbaumes
Copy link
Member

That looks way better if it works like it seems to say. I imagine @lukejharmon or @uyedaj could perform packrat::snapshot() on a known working Arbor R environment and post the result somewhere as a public URL (full R source packages snapshot), which we then download and install in Ansible. I don't think we want to check that snapshot into Git.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants