-
Notifications
You must be signed in to change notification settings - Fork 89
Add an option to do recursive dependency search when `packrat::snapsh… #361
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
Add an option to do recursive dependency search when `packrat::snapsh… #361
Conversation
…ot()` is invoked.
|
Sorry for taking so long to respond here! You should still see the 'Requires:' field populated even with the current GitHub master version of packrat; I just tested with a project containing the file and attempting to snapshot this gave me fields like e.g. Perhaps I'm misunderstanding something or the issue is more subtle? |
|
Hi, I don't explain my use case correctly, sorry. I don't have any R script that load package that are installed in packrat. I use packrat for managing R packages at system level (see #357 for more information). So I have a R script that build a packrat from packrat.lock file. The problem is when I generate a packrat.lock file when a user ask me to create a new packrat from a list of desired packages or add packages to an existing one. As example, if I have to create a packrat with bit64 in it I will do: I obtain the corresponding packrat.lock file: No Requires field for bit64 but it depends of bit, has I said. If I do the same thing with the CRAN version of packrat, I obtain this packrat.lock file: Is my use case too specific? Can you consider adding an option as I asked previously? Thanks |
|
Fix by #391 |
Hello,
I'm using packrat.lock to restore my packrat, but since ac1a18c, when
packrat::snapshot()is invoked no more 'Require' field is add to packrat.lock file. It would be great to add an option to let the user choose if I want to enable/disable recursive dependency search.