Skip to content

renv.lock package information fully specified #2057

@aronatkins

Description

@aronatkins

It would be grand if the package details included in the renv.lock were sufficient to recreate the cache hash location for either Packrat or renv. In particular, in order to accurately compute cache hashes we need remote package details (GitHub repo, etc) and dependencies. Unfortunately, we need source-dependencies and LinkingTo dependencies separately, as LinkingTo is used to recursively compute hash locations.

Were the renv.lock to have all of these details, the manifest.json file would not need the full package description file contents. Additionally, the renv.lock could drop its Hash entry and accurately recompute it on the fly.

If the manifest.json does not need the full package DESCRIPTION, it means that we could consider deploying without a fully populated R library.

related: #884

The Packrat has implementation with all of its fields:
https://github.com/rstudio/packrat/blob/af3bed4d917461764926b56b90f6d511d16d4f58/R/cache.R#L25-L120

This improvement came up during a discussion about the Publisher.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions