Skip to content

Use pak::local_install_deps() in install()#2651

Open
hadley wants to merge 3 commits intomainfrom
pak-local-install-deps
Open

Use pak::local_install_deps() in install()#2651
hadley wants to merge 3 commits intomainfrom
pak-local-install-deps

Conversation

@hadley
Copy link
Member

@hadley hadley commented Jan 22, 2026

Includes some general updates to the docs of install(), and mild improvements to non-quiet output.

Fixes #2486. Fixes #2572.

@jennybc if you're testing install() interactively, it doesn't work on devtools itself, for probably obvious reasons.

Includes some general updates to the docs of `install()`, and mild improvements to non-quiet output.

Fixes #2486. Fixes #2572.
@hadley hadley requested a review from jennybc January 22, 2026 15:32
build_opts <- c("--no-resave-data", "--no-manual")
# Install dependencies
local({
if (quiet) {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hack around lack of quiet argument or option for pak.

if (build) {
install_path <- pkgbuild::build(
pkg$path,
build = build,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit hard to see in the diff, but we're no longer passing any build or install options when we install the dependencies. I think this is likely to be fine, since you'd generally except these to coming from CRAN and not built locally.

@hadley
Copy link
Member Author

hadley commented Jan 30, 2026

After this change, Positron should probably revert to calling devtools::install(), rather than pak::local_install(upgrade = FALSE).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Import pak Why is install() so keen to update packages?

1 participant