The script .Rprofile evaluates R code on startup. You could use that to test for various environment variables. Alternatively, use Unix shell scripts to set system environment variables to be used in a generic .Renviron. See help(Startup) for more details.
/Henrik On Sun, Jan 25, 2009 at 11:22 AM, Jonathan Greenberg <greenb...@ucdavis.edu> wrote: > Our lab has a lot of different unix boxes, with different hardware, and I'm > assuming (perhaps wrongly) that by setting a per-user package installation > directory, the packages will only work on one type of hardware. Our systems > are all set up to share the same home directory (and, thus, the same > .Renviron file) -- so, is there a way to set, in the .Renviron file, > per-computer or per-hardware settings? The idea is to have a different > package installation directory for each computer (e.g. > "~/R/computer1/packages" and "~/R/computer2/packages". > > Thoughts? Ideas? Thanks! > > --j > > -- > > Jonathan A. Greenberg, PhD > Postdoctoral Scholar > Center for Spatial Technologies and Remote Sensing (CSTARS) > University of California, Davis > One Shields Avenue > The Barn, Room 250N > Davis, CA 95616 > Cell: 415-794-5043 > AIM: jgrn307, MSN: jgrn...@hotmail.com, Gchat: jgrn307 > > ______________________________________________ > R-help@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/posting-guide.html > and provide commented, minimal, self-contained, reproducible code. > ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
