I encoutered a problem similar to the one discussed here: renv puts all packages into project's renv/library
I'm working on a Windows 10 machine and would like to use renv for a project which is located on a shared network drive.
I have taken the following steps before initializing renv:
In a project-level .Renviron, I set RENV_PATHS_ROOT to the shared network drive to store the cache on the same volume as the project (and further upcoming projects).
I used renv::settings$use.cache(TRUE) in case the cache is still disabled by default on Windows.
After initializing renv I found both a folder "cache" and a folder "renv/library" on the shared network drive, both containing copies of all packages used in my project from my user library. To me it seems that it was not possible to form junction points on the network drive, so that all packages were copied to the library instead (as outlined in the related topic linked above). Does this problem still exist and is the current recommendation to not use the cache when working on a network drive? Or is there any feasible workaround?
Many thanks in advance for your feedback!