.libPaths(new) stopped working in 2.10

Thu, Dec 10, 2009 5:40 AM

On Dec 9, 2009, at 21:51 , David Winsemius wrote:

On Dec 7, 2009, at 10:04 AM, Simon Urbanek wrote:

On Dec 6, 2009, at 14:45 , David Winsemius wrote:

On Dec 6, 2009, at 2:32 PM, Alexy Khrabrov wrote:

I used to have the following in my .Rprofile:

if (length(.libPaths())==1)
.libPaths(paste(Sys.getenv("HOME"),"/Library/R/",paste(R.version 
$major,as.integer(R.version$minor),sep='.'),"/library",sep=''))

-- and it added my user-defined library directory.  Then I  
installed
packages there, so during an upgrade, I'd know exactly which  
packages
I installed and auto-upgrade with a script.

However, in R 2.10's Mac OSX GUI, .libPaths(new) does nothing...   
Did
its behavior change?

What is "new"?

.libPaths() would need a character argument. Are you referring to  
this Grab picture of a checkbox in the Startup GUI preferences:
<pastedGraphic.tiff>

(probably not passed through the r-help-list-server)

I actually have the inverse problem. It has been created and I  
would like to remove it.

Well, then do so :).

I did so and restarted. I checked my ~/.Rprofile setting and that is  
not the source of the persistent non-R.Framework libpath. I reviewed  
the Macs section of the Installation Manual and it tells me that  
it's basically a Unix device and that I should review the general R  
instructions.

Reading the Installation and Administration Guide in section 6 I see  
several areas about which I am uninformed:

R.home(component="home")

[1] "/Library/Frameworks/R.framework/Resources"

I don't have an R_HOME/etc/Rprofile.site

I think I have found my problem because:
Sys.getenv("R_LIBS_USER")
              R_LIBS_USER
"~/Library/R/2.10/library"

So I tried Sys.setenv(R_LIB_USER = "")

I thought from the help page that this would report a logical value  
for success or failure, but got neither. Wish me luck.

Uh - all that has nothing to do with what I was saying - remove the ~/ 
Library/R/2.10/library directory, that's all you need to do ...

Cheers,
Simon

.libPaths(new) stopped working in 2.10

Thread (5 messages)