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
I guess this isn't supposed to be the intended behaviour, no?
I was first delighted by the new lock argument since it'd give a better UX for renv's explicit snapshot type, but I really don't wanna write local filesystem paths to an renv project's lock file shared with others...
Footnotes
For the sake of simplicity, I use rsvg here, a package without any further R package dependencies. In both cases, rsvg was added to the project's DESCRIPTION file before installing it. ↩
The text was updated successfully, but these errors were encountered:
I'm using renv with its
"explicit"
snapshot type and just tested the newlock
argument forrenv::install()
introduced in renv 1.0.4.I noticed that when I install a new package1 using
renv writes the following lines to my project's
renv.lock
:When installing the same package using
OTOH, renv writes these lines to the
renv.lock
:I guess this isn't supposed to be the intended behaviour, no?
I was first delighted by the new
lock
argument since it'd give a better UX for renv's explicit snapshot type, but I really don't wanna write local filesystem paths to an renv project's lock file shared with others...Footnotes
For the sake of simplicity, I use rsvg here, a package without any further R package dependencies. In both cases,
rsvg
was added to the project'sDESCRIPTION
file before installing it. ↩The text was updated successfully, but these errors were encountered: