Skip to content
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.

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

More informative message when install warnings are converted to errors #202

Closed
gaborcsardi opened this issue Oct 12, 2018 · 4 comments
Closed

Comments

@gaborcsardi
Copy link
Member

E.g. mention the env var to change this behavior.

@stroberts
Copy link

Building on this:
It appears that the environment variable which controls (or can control) this behavior is 'R_REMOTES_NO_ERRORS_FROM_WARNINGS'. So if one does not want warnings to arrest an installation, they would execute something along the lines of
allow_warnings_not_to_break <- Sys.setenv(R_REMOTES_NO_ERRORS_FROM_WARNINGS = T)
before running remotes::install_.

That's my reading given the use of should_error_for_warnings().

Certainly I think this behavior needs better documentation.

@gaborcsardi
Copy link
Member Author

You need to set it to true, see https://github.com/r-lib/remotes#environment-variables

richfitz added a commit to vimc/orderly that referenced this issue Nov 28, 2018
Caught in the crossfire with remotes changing behaviour

krlmlr/r-appveyor#57
krlmlr/r-appveyor#127
r-lib/remotes#202
@gaborcsardi
Copy link
Member Author

Turns out that this is not so easy, because the warning -> error conversion happens in the subprocess.

@gaborcsardi
Copy link
Member Author

Closing for now, as there will be other improvements related to this:

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

No branches or pull requests

2 participants