@znmeb suggested including an RStudio preview image. Ed, thoughts on how this would work?
we could create rocker/rstudio:preview. Normally the version tag refers to the R version, not the RStudio version though, so perhaps that would be confusing?
Presumably this would build on rocker/rstudio:latest image (or it's parent, rocker/r-ver:latest) and just add the current preview version of RStudio?
latest and devel tags in the versioned stack are built nightly. Would we want that for preview as well?
Presumably downstream images would inherit preview as tag as well? (e.g. sounds like a rocker/tidyverse:preview image would have what you want, though you only need the devtools side of it and maybe not the tidyverse side...)
Alternately, we could separate it out from this stack; though I'm wary of an approach that increases maintenance. e.g. we could build a separate RStudio on the r-base stack. Preferences differ here, but I find dealing with the apt-pinning between testing and unstable can be tricky. e.g. the default apt-get will pull from testing, but sometimes you need to pull a library from unstable, and then you may find the libs you have in testing aren't new enough to be compatible and everything has to be upgraded, which may break certain things (like RStudio wanting the 1.0.0 libssl)
cboettig
commented
5 years ago
@znmeb suggested including an RStudio preview image. Ed, thoughts on how this would work?
rocker/rstudio:preview. Normally the version tag refers to the R version, not the RStudio version though, so perhaps that would be confusing?rocker/rstudio:latestimage (or it's parent,rocker/r-ver:latest) and just add the current preview version of RStudio?latestanddeveltags in the versioned stack are built nightly. Would we want that forpreviewas well?previewas tag as well? (e.g. sounds like arocker/tidyverse:previewimage would have what you want, though you only need the devtools side of it and maybe not the tidyverse side...)Alternately, we could separate it out from this stack; though I'm wary of an approach that increases maintenance. e.g. we could build a separate RStudio on the
r-basestack. Preferences differ here, but I find dealing with the apt-pinning betweentestingandunstablecan be tricky. e.g. the default apt-get will pull fromtesting, but sometimes you need to pull a library fromunstable, and then you may find the libs you have in testing aren't new enough to be compatible and everything has to be upgraded, which may break certain things (like RStudio wanting the 1.0.0 libssl)