Set R_BIOC_VERSION env variable used by pak
#7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #6, the Bioc-version can be inconsistent with the one requested after the
setup-r-dependenciesstep. I suspect this is due to the use of pak insetup-r-dependencies, which sets its own package repository settings (seepak::repo_get()) and defaults to Bioc-release, thereby ignoring the configuration done by thesetup-biocstep.This PR sets the environment variable
R_BIOC_VERSIONenvironment variable during thesetup-biocstep, to ensure that pak will use the requested Bioc-version in subsequent installation steps.See also r-lib/pak#309 (comment)