similar to: Installing/updating packages on a lab network

On 7/28/2015 1:32 PM, Uwe Ligges wrote: > Just add the line > > R_LIBS_SITE=F:/R/library > > to the file R_HOME/etc/x64/Renviron.site Thanks, Uwe I have no way to test this and our IT people who do the installation know nothing of R, so follow-up questions: * There is no R_HOME/etc/x64/Renviron.site file, but there is a R_HOME/etc/Rprofile.site I can modify and ask them to

Just add the line R_LIBS_SITE=F:/R/library to the file R_HOME/etc/x64/Renviron.site Best, Uwe Ligges On 28.07.2015 15:53, Michael Friendly wrote: > I'm the faculty member in my department who advises our IT staff on the > details of installing R for > students and faculty on our Windows 7 lab network. We are about to > upgrade from R 3.1.1 to > R 3.2.1, and once that is

Martin, I am aware of --vanilla; I use it myself for some testing. In this case R_LIBS_USER was set externally (part of my login) and does not involve any of the R scripts. That means it is inherited by any subprocess. For example: tmt1495% R --vanilla --no-environ R version 3.3.1 (2016-06-21) -- "Bug in Your Hair" Copyright (C) 2016 The R Foundation for Statistical Computing

I have a local library which depends on the expm library. The expm library is loaded into my personal space and I have the environment variable R_LIBS_USER set appropriately. The command "library(expm)" works just fine from the command line, and in fact the package works if I do the source() and dyn.load() commands by hand. The following sequence works: tmt% R CMD build

AFAIU, 'R CMD check --as-cran' tries to hide any site and user package libraries by setting R_LIBS_SITE and R_LIBS_USER. However, contrary to R_LIBS_SITE, it fails for R_LIBS_USER and the user's personal library is still available for test scripts. Should I revise my assumptions, or is that intentional? The short version. Shouldn't: $ R_LIBS_USER='' Rscript --vanilla -e

I asked a couple of months ago in r-sig-fedora about a difference I noticed between Ubuntu and RedHat/Fedora. Now I think I've figured out the cause is a little issue in packaging but I don't know how to get it fixed. On Ubuntu, the setup is like this. It i is controlled in a file called Renviron R packages built/distributed in RPM are installed to /usr/lib/R/library. R packages built

Is there a fundamental reason why I cannot set either one of ## add local library path -- doesn't work either R_LIBS_USER="c:/opt/R-library" R_LIBS_SITE="c:/opt/R-library" in $R_HOME/etc/Rcmd_environ even though I can seemingly set other things here? It breaks "R CMD check" for me as I prefer NOT to install packages in a versioned path. FWIW,

Hi all, I'm trying to check a package using R CMD check --as-cran <package>. When I do so, the check fails upon not finding the dependencies which I have installed in a non-standard location. Per the manual, I created ~/.R/check.Renviron : $ cat ~/.R/check.Renviron R_LIBS=/usr/lib64/R/library:/usr/lib64/R/var R_LIBS_SITE=/usr/lib64/R/library:/usr/lib64/R/var No luck. I tried

Hi there, Moving this request for info over from an R-HPC-SIG list thread as the issue is less HPC than something that has bitten me as a result of trying to install HPC (read CUDA) R packages. Background to this is that I have both a Ubuntu host for a Tesla card that some researchers are looking to do CUDA-related R computation on, and a prototype, RHEL-based, cluster that is being used to

On Wed, Mar 18, 2020 at 8:04 PM Dirk Eddelbuettel <edd at debian.org> wrote: > > > On 18 March 2020 at 19:19, Henrik Bengtsson wrote: > | AFAIU, 'R CMD check --as-cran' tries to hide any site and user package > | libraries by setting R_LIBS_SITE and R_LIBS_USER. However, contrary > > What makes you think that? AFAIK --as-cran just sets a bunch of the (nearly

Does anyone have advice on how to instruct R CMD check to use a non-standard set of libraries? Here's the situation: I'm trying to do some automated checking on package dependencies of a package I maintain. In order to do that I've written code that takes the list of the dependent packages and for each package (1) downloads the most recent/available .tar.gz file; (2) installs the

> .expand_R_libs_env_var("poof/%p/%v") [1] "poof/x86_64-w64-mingw32/3.4" Bill Dunlap TIBCO Software wdunlap tibco.com On Fri, Jan 12, 2018 at 4:49 AM, Loris Bennett <loris.bennett at fu-berlin.de> wrote: > Hi, > > When I install a package as a non-root user, it gets saved in a path > such as > > ~/R/x86_64-unknown-linux-gnu-library/3.4 >

Hi, When I install a package as a non-root user, it gets saved in a path such as ~/R/x86_64-unknown-linux-gnu-library/3.4 for any R version 3.4.x. Thus, if I want to install the packages somewhere else, as root say, I might do install.packages("somepackage","/some/where/else/R/site-library/3.4") In this case I would then want to construct the appropriate path in, say,

On Saturday, 16 May 2020 00.38.34 WEST I?aki Ucar wrote: > Sorry, but I'm not sure I'm following you. How does having > /usr/lib64/R/library as system library prevent you from testing > r-devel? First the context, we are speaking of srpms. Use case: you want to test a pre-version of R before it is released and you want to do it using dnf while not having to de-install the

Hi, everybody. I've got some Centos Linux systems and some Ubuntu Linux systems. R's basically the same in either place, but the packaging of R for Debian systems seems better to me than it is on Fedora/Redhat/Centos. I joined R-sig-debian and we talk about package management issues there sometimes. One of the really handy R packaging ideas they have is to customize R environment so

Hi everyone, Two minor points about ?.Renviron. 1) If R_ENVIRON is not set then R defaults to `${R_HOME}/etc/Renviron', not `${R_HOME}/etc/Renviron.site' as stated. 2) In the details, there is a missing "way" in "`value' is processed in a similar to a Unix shell." Cheers, Jonathan. --please do not edit the information below-- Version: platform =

Hi I am trying to install R-igraph, but when I issue the command : install.packages("igraph", lib="~/.R/library") in the R session, I get the following error: Warning in install.packages("igraph", lib = "~/.R/library") : 'lib = "~/.R/library"' is not writable Error in install.packages("igraph", lib =

Hi, I have Debian Testing running on a Lenovo Thinkpad X1 Carbon (2015, 3rd gen.). I would like to have a package library independent of the installed R version. Under Ubuntu, I used to have the following line in ~/.Renviron: R_LIBS=/usr/local/R/library:/usr/lib/R/site-library This worked fine and /usr/local/R/library showed up in .libPaths(). However, under Debian (with the same ~/.Renviron),

Dear Johannes, Dear Dirk, Thanks a lot for helping. Here is the missing information. Here is how I installed R. This is basically how Martin Maechler showed me to install R under Ubuntu (in several versions so that they are also recognized by ESS). My goal is to adjust this to make it work for Debian: 1) sudo emacs /etc/apt/sources.list # then add: deb

Dear all, When installing the usual packages that I use, after installing R 3.0.1, I noticed that the installation of some packages that query R about its configuration did not succeed. The problem is exemplified by: berwin at bossiaea:~$ R-3.0.1 CMD config CC /opt/R/R-3.0.1/lib/R/bin/config: 222: .: Can't open /opt/R/R-3.0.1/lib/R/etc/Renviron Prior to R 3.0.1 such commands worked fine: