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

Creating a Binary CRAN Repository to Improve Useability #12

Closed
thomascjohnson opened this issue Dec 3, 2019 · 5 comments
Closed

Creating a Binary CRAN Repository to Improve Useability #12

thomascjohnson opened this issue Dec 3, 2019 · 5 comments

Comments

@thomascjohnson
Copy link

If you've used this buildpack to create a Shiny app or any R application that depends on a lot of fancy R packages, you have probably run into the issue of not being able to successfully push due to the hard 15 minute time limit on builds. Installing devtools, ggplot2, dplyr and all of their dependencies takes a while and are not able to be installed in less than 15 minutes. These are extremely common packages to use in almost any R application, and most R users don't have the experience needed to simply add packages via the apt buildpack or some other method.

This was an issue for the EPA, and it was fixed by creating binary packages for cflinuxfs3: https://github.com/USEPA/cflinuxfs3-CRAN

This repository offers substantial utility for all R buildpack users, but it currently depends on me maintaining it. I've created a package that handles adding packages to the repo, but it still means that someone has to individually, manually add packages.

I would like to open a discussion about how we could create either an automated system to build binary packages or setup a organizational structure to distribute the responsibility to more contributors. I think that this can be something fairly lean and simple, while also vastly improving the utility of the R buildpack for all users.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/170080801

The labels on this github issue will be updated when the story is started.

@dwillist
Copy link
Contributor

dwillist commented Dec 9, 2019

@thomascjohnson This sounds like a great solution, We have existing pipelines that do something similar for other dependencies. Though I am hesitant to have a list of pre-compiled packages be the only solution for buildpack users. This solution would also be a long-term goal and require a lot of additional infrastructure on our end.

@kvedurmu
Copy link

kvedurmu commented Mar 4, 2020

Hey @thomascjohnson, we can look into doing this when the team implements the r-CNB.

@kvedurmu
Copy link

Closing this out. As mentioned before, we can look into supporting this in the R Paketo Buildpack

@NiPfi
Copy link

NiPfi commented Feb 25, 2021

@kvedurmu Any news on said R Paketo Buildpack? I wasn't able to find a repository for it.

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

5 participants