-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Consider adding ability to generate a renv lockfile from log #161
Comments
omg this would be amazing!! |
I'd love to help out with this feature. Submitting another issue (#162) to parse/filter a log file. This could be associated with that issue. |
After more thought and tinkering with renv lockfiles, maybe generating a DESCRIPTION file from log would be a more flexible alternative. {renv} does pull package version from the DESCRIPTION file if its available in an R project: https://rstudio.github.io/renv/reference/install.html?q=description#project-description-files |
Interesting, so it makes a sort of pseudo-package for you? So if you used 4 packages in the your Script, then A Description Files generated by logrx would be generated with those 4 as Imports. Would suggest have all the packages in the environment but not used? |
It could be like a compendium DESCRIPTION file (based on Karthik's talk at RStudio Conf 2019 that I recently saw). We could maybe add the packages in the environment as suggests like you said. |
|
Revisiting this today. As of renv 1.0.0, they added
|
Feature Idea
Consider adding ability to create a renv lockfile from the log file or along with log file creation (at time of
aexecture()
). This would allow users to more easily recreate the environment that was originally used.Relevant Input
Relevant Output
No response
Reproducible Example/Pseudo Code
No response
The text was updated successfully, but these errors were encountered: