I think it is still on the todo list in renv
- [x] Include recommended packages in the lockfile? (Since R installations on
Linux may not have these packages available). Or at least confirm that
packages which depend on recommended packages enter the lockfile.
- [x] Use a single lockfile file, but provide a `history()` function to dig out
old versions of the lockfile. (Make it clearer to users what needs to be
- [x] Handle `NA` mtime in filecached APIs.
- [ ] Implement `bundle()` for packaging up a project, potentially with package
sources, binaries, or even the library itself for restoration on a new
machine (potentially lacking internet access).
- [x] Provide tools for upgrading version of `renv` used to manage a project.
- [ ] Think about how we might discover 'stale' entries in the cache.
- [x] Handle `renv::init()` case when another project already active (want
to make sure we use the user library rather than active library)
Currently I don't think there is such functionality apart trying to reproduce yourself by playing with the path to set the downloaded source folder (
RENV_PATHS_SOURCE) inside project maybe. That way restoring packages would find the sources without being required to download them. never tried, just an idea here