Questions regarding removal and following re-installation of a specific R package using a custom library path
0
0
Entering edit mode
svlachavas ▴ 840
@svlachavas-7225
Last seen 13 months ago
Germany/Heidelberg/German Cancer Resear…

Dear All,

please excuse me for insisting from a previous post (Error with R package RontoTools regarding administrator issues downloading updated KEGG data), but because i dont have any significant experience in any related issues, i would like to ask to general questions about the installation of R packages:

1) as i want to remove a specific R packagebecause when i updated in  R 3.2.2 i kept also my previous r R version-but from Rstudio i run only the latest version- should i remove manually the package,

or use something like: remove.packages("ROntoTools") # the specific package ??

 

2) Secondly, to reinstall the above package again, but using a custom library path(because with the default biocLite i have problems in dowloading data-"permision denied" etc..-, could i use some argument with biocLite() specifying this ?

I searched also some forums and found the function: 

.libPaths() which by default returns : .libPaths()

[1] "C:/Program Files/R/R-3.2.2/library"

Thus, could i use this argument specifying a different location for installing this specific package, like my default working directory: 

"C:/Users/Efstathios/Documents" ??

Any help or suggestions would be essential !!

package installation custom library path biocLite bioconductor • 1.9k views
ADD COMMENT
0
Entering edit mode

You probably don't need to worry about uninstalling packages. Skip that and just try reinstalling with biocLite(). Don't worry about where the package is installed, if biocLite() can't write to the default library directory it will prompt you to create a new one and you can say yes. After reinstalling the package, does it then work for you?

ADD REPLY

Login before adding your answer.

Traffic: 666 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6