You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before restore() is complete, I often run into issues with environment restoration on new computers.
The easiest resolution is often to install a new version of troublesome packages, or install them from a new location (i.e. RSPM instead of GitHub, etc.).
However, then it is tricky to update the renv.lock file so that the "successful" package installation is used (and not discarded on the next restore()).
The natural way a user might want to do this is as an argument to install, e.g. an argument lock=TRUE to suggest that the install should immediately be written to the lockfile (with any upgraded / installed dependencies).
renv::install("package", lock=TRUE)
This is possible today:
renv::snapshot(packages="package", update=TRUE)
However, it uses the snapshot() verb, which is counter-intuitive, because I am thinking about correcting an install / the lockfile, not creating a new lockfile.
The text was updated successfully, but these errors were encountered:
Before
restore()
is complete, I often run into issues with environment restoration on new computers.The easiest resolution is often to install a new version of troublesome packages, or install them from a new location (i.e. RSPM instead of GitHub, etc.).
However, then it is tricky to update the
renv.lock
file so that the "successful" package installation is used (and not discarded on the nextrestore()
).The natural way a user might want to do this is as an argument to install, e.g. an argument
lock=TRUE
to suggest that the install should immediately be written to the lockfile (with any upgraded / installed dependencies).This is possible today:
However, it uses the
snapshot()
verb, which is counter-intuitive, because I am thinking about correcting an install / the lockfile, not creating a new lockfile.The text was updated successfully, but these errors were encountered: