8000 `rig install --without-p3m` doesn't work as expected · Issue #193 · r-lib/rig · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

rig install --without-p3m doesn't work as expected #193

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.

Sign up for GitHub

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

Jump to bottom
Closed
lewinfox opened this issue Oct 10, 2023 · 2 comments
Closed

rig install --without-p3m doesn't work as expected #193

lewinfox opened this issue Oct 10, 2023 · 2 comments
Labels
bug an unexpected problem or unintended behavior

Comments

@lewinfox
Copy link

From reading the docs I expect rig install --without-p3m to leave the default package repos alone. However, this option doesn't appear to do anything.

This is a similar question to #87, but I'm asking about the behaviour of the flag rather than of rig in general.

Example Dockerfile to reproduce what I'm seeing:

FROM ubuntu:latest

RUN apt-get update && apt-get -y install curl
RUN curl -Ls https://github.com/r-lib/rig/releases/download/latest/rig-linux-$(arch)-latest.tar.gz | tar xz -C /usr/local

RUN rig install --without-p3m release
RUN rig default release

CMD rig run -e "getOption('repos')"
docker build -t rig-demo . && docker run --rm rig-demo

Expected output:

                         CRAN 
"https://cloud.r-project.org"

Actual output:

                                                          P3M 
"https://packagemanager.posit.co/cran/__linux__/jammy/latest" 
                                                         CRAN 
                                "https://cloud.r-project.org"

Removing the --without-p3m flag gives identical output from getOption('repos').

Am I misunderstanding the purpose of the flag or is this a bug?

This is an awesome tool, thanks very much!
@gaborcsardi gaborcsardi added the bug an unexpected problem or unintended behavior label Oct 10, 2023
@gaborcsardi
Copy link
Member

Yeah, that seems like a bug, unfortunately. Thanks for the great reproducible example!

@rumichaska rumichaska mentioned this issue Feb 1, 2024
Closed
@gaborcsardi
Copy link
Member

Closed by 382bed1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug an unexpected problem or unintended behavior
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gaborcsardi @lewinfox
0