I am new to Anaconda and followed the tutorial to create an R environment and run RStudio in Anaconda Navigator. When I did so, I noticed that the versions of R and RStudio are 3.6.1 and 1.1.456, respectively. I know, though, that the latest versions of R and RStudio are 4.2.0 and 2022.02.3, respectively. Is there a way to use these more recent versions in Anaconda Navigator (or Conda)?
In the case of Anaconda, we are using the redistributed version of Rstudio.com, so it is easy to get older versions.
However, there is a way to use a newer version than the one you downloaded.
Use conda update rstudio and conda update R-Language.
The current version is the one you wrote.
Rstudio and R-Language directly, not in the anaconda repository https://www.r-project.org/
as well as Download the RStudio IDE - RStudio
Download from and use.
However, do not put it in the Anacoda directory, and use only the calculation result in Anacoda.
I use R v4.2.1 and current RStudio on macOS 12.6. I installed conda or Anaconda (I’ve forgotten details), and now RStudio opens, but RStudio About and Preferences give nothing, and asking, in an R script that I’ve run many times in the past, that a standard library be loaded (e.g. library(rtracklayer)) simply returns nothing. I would like (need) to be able to run RStudio again.
If I re-install R (v4.2.1) and RStudio (2022.07.2+576), I see the same awkward behaviour. But if I launch R.app, library(rtracklayer) or library(dplyr) appear to run correctly.
It is almost three years later, and still the latest version of R that is installable with Anaconda is 3.6.1. I’d like to use Anaconda to manage R installations and packages, but it does not look like R is a high priority for Anaconda. Could a member of the Anaconda team clarify if there is any intention to develop Anaconda as a service for R in future?
Thanks for bringing this up - we understand the frustration with the current state of R support in Anaconda. We’re actively working on formalizing our R support policy and should be able to provide updated guidance after finishing our internal alignment on the best path forward.
In the meantime, we acknowledge that our R channel has fallen significantly behind current releases, and we’re evaluating the best path forward for our users who depend on R workflows.
We’ll make sure to communicate any policy changes clearly once our internal alignment is complete.