If memory serves me right, the specific version semantics
were here because at some point we were installing different
versions of rsession-proxy for different versions of R. We
don't do that anymore, so we should just unpin it and let the
pip solver install the appropriate version.
Hopefully fixes https://discourse.jupyter.org/t/r-conda-example-repo-isnt-working-any-more/21739/3
r-recommended is a collection of common CRAN packages,
which cause conflicts when trying to install older R.
These same packages can be regular dependencies retrieved from CRAN.
- Install a different version of RStudio for R < 4.1,
as latest RStudio doesn't seem to support those. And
newer RStudio isn't supported on these older R versions.
- Cleanup how Shiny is installed - install it with the same
apt invocation as rstudio (saves time), and install shiny-proxy
from PyPI instead or GitHub. The release on PyPI is the same
as our previous GitHub pin.
- Remove outdated comment about different behavior for R 3.6 - I
think now we get all our R versions from the same apt repo. Plus,
the conditional was adding more scripts than just adding extra apt
package repos
We were doing this from an old MRAN snapshot. I moved the pin
a little ahead, so IRKernel can also be installed from CRAN
instead of from GitHub. R <= 4.0 gets the old version, and anything
newer gets a more recent version of devtools. This gives us
fast installs for IRkernel with binary packages.
Also add a R 4.0 and R 4.1 test
pre-commit-ci[bot]