support for installation from renv.lock lockfile?

Open
#343 26 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
r
Domain
tooling

Research direction

Start with pak::lockfile_create() and pak::lockfile_install(), then inspect how renv.lock represents versioned CRAN packages. Confirm the scope for accepting an renv.lock-derived package list and handling versioned CRAN packages; done means a lockfile created by renv can be installed through pak. No file or test is named, so locating existing lockfile tests is part of the initial work.

Written by the indexing model from the issue text.

Description

feature

It looks like pak has its own machinery for creating and installing from lockfiles, e.g.

pak::lockfile_create(<pkgs>)
pak::lockfile_install()

Is there a straightforward mechanism whereby lockfiles created by renv.lock could work here as well?

The main barrier I see is that one cannot yet create lockfiles from versioned R packages; e.g.

> pak::lockfile_create("rlang@0.4.12")
x Creating lockfile pkg.lock [66ms]
Error: Cannot install packages:
* rlang@0.4.12: Versioned CRAN packages are not implemented yet

If we had that, I think it would be straightforward for renv to create a list of versioned remotes that could be passed into pak.

Dominant language
C
Stars
821
Forks
88
Avg merge
17m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from r-lib/pak

All issues in r-lib/pak

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.