I agree, environment modules really come into their own when you need to switch
back and forth between different versions, as I do when testing my packages.
Since environment modules are used on the cluster I work on, it's actually
easier for me to use them on my local machines than to change w
Aaron
For the problem I had in mind, changing a couple of environment
variables does not seem like more work than this, but it may solve a
bigger problem than the one I was thinking about. If I understand
correctly, you can use this to switch among versions of R, similar to
what I am doing a
Have you looked at Environment Modules (http://modules.sourceforge.net/)? I
use it to maintain multiple versions of R. Users can choose their default and
switch among them at the command line.
Aaron
On Fri, Jan 18, 2013 at 02:04:13PM -0500, Paul Gilbert wrote:
> (somewhat related to thread [R
(somewhat related to thread [Rd] R CMD check not reading R_LIBS )
For many years I have maintained R versions by building R (./configure ;
make) in a directory indicating the version number, putting the
directory/bin on my path, and setting R_LIBS_SITE.
It seems only one version can easily b