The idea is that could use conda to setup an environment with different R / BioC packages to avoid situations when a package is update without backwards compatibility (as it happened with scater).
We need to test if in a conda env for R3.5 the BioC version installed is the latest, or that which was released with that R version.
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Installing R3.5 in a env went well. However when starting the R console it started to try and install packages in a look, for instance devtools. The issue was my .Rprofile which contained instructions to install some packages if not present. Commenting this out solved the issue.
Installing R packages inside the conda env has some problems (possibly depending how many R packages and dependencies are installed upon env creation):
Rcurl is missing but it can be installed with conda
Zlib was not found during BioC package installation (see this similar issue).
This might be because conda changes environment paths / variables and things start missing. devtools, for instance, can't find tar or gzip and this needs to be set: Sys.setenv(TAR = "/bin/tar") (or symlinked). Once that was fixed I managed to install Rhdf5lib from the git repo with devtools::install_github("grimbough/Rhdf5lib")
As far as I can tell, BiocManager::install() matches the BioC version to the R version. In case of doubt we can also specify the version with BiocManager::install("HDF5Array", version = "3.8").
@herseman if you want to use the conda env for R.3.5 (with scater 1.10), it's in /projects/conda/envs/sc_BioC_3.8. conda activate /projects/conda/envs/sc_BioC_3.8 should activate it.