libPaths(new=c('/envs/env_name/lib/R/library', '')įinally, I put this function (which you will have to edit somewhat) in my. However, you need to make sure your conda path is first. Consequently, when installing an R package externally (and if you need to do this a lot, then conda may not be the solution for you), I look up the dependencies in the docs and install those first with conda.įinally, you will need to add your external library to your. This is ok, but many of the dependencies could actually be installed with conda which is preferable.
The installer will put them into the directory specified with lib. There is a bit more to this as in the process of installing other r packages may be installed. Other install methods such as biocLite and install.github wrap install.packages, so will accept the lib argument even if it's not explicitly noted in the docs. When I want to install a package by hand, I do install.packages(, lib='/home/bater/R35). As an example, I have a directory /home/balter/R35. When you need packages that are not available in the channel set you are using, you must install them by hand into an external location outside of the conda environment.Do not mix proprietary channels ( anaconda, r) with open-source channels ( conda-forge, bioconda, defaults).If you stick to that order, you should not have any problems. condarc, you should always use the following order: 1. They are largely compatible with the following caveat. The conda-forge, bioconda, and defaults channels are open-source channels.
The r channel is.well I don't really understand but I think it's some kind of subset of the anaconda channel.