[R-sig-Debian] running a locally built R-devel with libraries from Debian installation

[Dirk Eddelbuettel]

On 9 May 2010 at 18:50, Sebastian P. Luque wrote:
| On Sun, 9 May 2010 17:57:40 -0500,
| Dirk Eddelbuettel <edd at debian.org> wrote:
| 
| > The Debian package should only set these env vars if these are
| > otherwise unset:
| 
| > edd at ron:~> Rscript -e 'print(.libPaths())' ## default [1]
| > "/usr/local/lib/R/site-library" "/usr/lib/R/site-library" [3]
| > "/usr/lib/R/library" edd at ron:~> R_LIBS_SITE="/tmp" Rscript -e
| > 'print(.libPaths())' [1] "/tmp" "/usr/lib/R/library" edd at ron:~>
| > R_LIBS_USER="/tmp" Rscript -e 'print(.libPaths())' [1] "/tmp"
| > "/usr/local/lib/R/site-library" [3] "/usr/lib/R/site-library"
| > "/usr/lib/R/library" edd at ron:~>
| 
| > There may well be a bug lurking somewhere but at leats here I got to
| > modify libPaths on the fly.
| 
| > Good enough?
| 
| Great, I guess that's what I'm trying to get at: one would have to start
| R-devel with a long string.  I thought there would be a way to just do
| 'R' or '~/src/R-devel/bin/R' and then have a mechanism in the user
| startup files to ensure that Debian site libraries are added only when
| using R-devel.  Thanks Dirk, that should get me en route!

Another possibility is to use ~/.Rprofile and to directly set this as an
argument to to the .libPaths() function -- see help(.libPaths).

-- 
  Regards, Dirk