After played some time, I realized the following (it's probably clear without saying for the author, but new users might have similar confusions like me):
get_miniconda_path() and R_MINICONDA_PATH point to the root of all possible rminiconda miniconda installations. Each rminiconda usage with a new name create a new copy under this root folder.
I tried to install package through conda using reticulate, then I found I need to point to rminiconda miniconda like this, because reticulate is checking the miniconda installation path, which need to be root/name. This is mentioned in the readme, but the naming can be a little confusing.
reticulate:::miniconda_exists(file.path(rminiconda::get_miniconda_path(), "gee"))
Strictly speaking, get_miniconda_path() might actually means get_rminiconda_root()
In the end, my goal is to use rminiconda to create a new miniconda installation, and install packages through conda(which I have to use reticulate) (the example in rminiconda only mentioned use_python, which doesn't involves conda, and rminiconda itself only have a function to install pip (I will avoid pip and use conda as much as possible).
After played some time, I realized the following (it's probably clear without saying for the author, but new users might have similar confusions like me):
get_miniconda_path()andR_MINICONDA_PATHpoint to the root of all possible rminiconda miniconda installations. Eachrminicondausage with a new name create a new copy under this root folder.reticulate:::miniconda_exists(file.path(rminiconda::get_miniconda_path(), "gee"))Strictly speaking,get_miniconda_path()might actually meansget_rminiconda_root()In the end, my goal is to use rminiconda to create a new miniconda installation, and install packages through conda(which I have to use reticulate) (the example in rminiconda only mentioned use_python, which doesn't involves conda, and rminiconda itself only have a function to install pip (I will avoid pip and use conda as much as possible).