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 have a git repository containing package source (within subdirectory my_package) and a renv lockfile. For context, the repo is private, and I'd rather not mess with PATs or gitlab/github credentials (e.g. to use remotes::install_gitlab), particularly seeing as the package is contained within the project anyway.
To capture my_package in the lockfile, I use:
renv::install('./my-package')
renv::snapshot()
However, the RemoteUrl stores the full path to the package: /home/john/my_project/my_package. This is problematic when the lockfile is commited back to the repo and another user then clones it into their home directory.
I can edit the RemoteUrl manually to relative path, ./my_package, but renv then complains about the lockfile being out sync, and the relative path is overwritten on subsequent snapshots.
So, is it possible to somehow force renv to use a relative path for local sources?
The text was updated successfully, but these errors were encountered:
I have a git repository containing package source (within subdirectory
my_package
) and a renv lockfile. For context, the repo is private, and I'd rather not mess with PATs or gitlab/github credentials (e.g. to useremotes::install_gitlab
), particularly seeing as the package is contained within the project anyway.To capture
my_package
in the lockfile, I use:However, the RemoteUrl stores the full path to the package:
/home/john/my_project/my_package
. This is problematic when the lockfile is commited back to the repo and another user then clones it into their home directory.I can edit the RemoteUrl manually to relative path,
./my_package
, but renv then complains about the lockfile being out sync, and the relative path is overwritten on subsequent snapshots.So, is it possible to somehow force renv to use a relative path for local sources?
The text was updated successfully, but these errors were encountered: