
The Anaconda Navigator's conda package index will likely not reflect the changes that RStudio makes.īefore I make a likely irreversible and breaking change to Anaconda, can anyone recommend a better way to do this Rstudio update and have Anaconda's package index correctly reflect changes that RStudio will make with executables and packages that it updates and installs? RStudio doesn't use Anaconda Navigator's conda program to do the upgrade. It looks like to get a good RStudio update, I must update RStudio from within RStudio, but this will likely break a lot of Anaconda R functionality. Plus, Anaconda makes a lot of choices without always asking the user about where to put things. My judgement is that R and RStudio are basically UNIX programs that have been ported to Windows, and have all kinds of "leftover" Unix-izms and quirks in the way they reference files, directories, and scripts. Also, Anaconda put my R-dedicated virtual environment (which I named Rdev') and installed R in a wierd place too: C:\Users\nda\envs\Rdev\Lib\R\bin`. Anaconda Navigator package manager doesn't give me an option to install any later versions.


I want to use the current RStudio release. If I check the Rstudio website current RStudio download, it says the latest version is RStudio-.exe. The version of R Studio that is bundled with the latest release of the Anaconda distribution is over a year old, specifically version rstudio-1.1.456. My delivery vehicle to the end user must be Jupyter Notebook or JupyterLab with Python and R kernels installed by Anaconda Navigator. This is a different issue than what was posted by someone else on this forum. This is cross-posted from # How best to update / upgrade RStudio inside or underneath Anaconda Navigator?.
