[Rd] regenerate Rscript after moving R installation

[Simon Urbanek]

I forgot to mention that some packages bake-in paths as well, so even if you fix both R and Rscript, it will still not work in general.

On Sep 22, 2013, at 3:42 AM, Simon Urbanek <simon.urbanek at r-project.org> wrote:

> On Sep 21, 2013, at 8:43 PM, Tobias Verbeke <tobias.verbeke at openanalytics.eu> wrote:
> 
>> L.S.
>> 
>> In this bug report
>> 
>> https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=14493#c1
>> 
>> it is mentioned that after moving an R installation
>> one should regenerate the Rscript executable.
>> 
>> Is there an easy way to do so (after an R installation has been
>> moved)?
>> 
> 
> You cannot move installed R. Once you run make install, there are several places in which paths get baked in - mainly Rscript and the R start script. What I typically do for deployment on the Labs machines is to use make install rhome=<xxx> where <xxx> is some path that I can always create a symlink in (I also use DESTDIR so that path doesn't actually need to exist on the build machine and it avoid polluting --prefix which is not needed). That way you can move R wherever you want as long so you keep that one symlink up to date.
> 
> Cheers,
> Simon
> 
> 
>> I have not found any information in the R installation and 
>> administration manual.
>> 
>> Many thanks in advance for any pointer.
>> 
>> Best wishes,
>> Tobias
>> 
>> P.S. The background to this question is the usage of Rscript
>> calls in the Makevars files of some R packages on CRAN, so
>> the 'broken' Rscript prevents installation of certain R packages.
>> 
>> -- 
>> 
>> Tobias Verbeke
>> Manager
>> 
>> OpenAnalytics BVBA
>> Jupiterstraat 20
>> 2600 Antwerp
>> Belgium 
>> 
>> E tobias.verbeke at openanalytics.eu
>> M +32 499 36 33 15
>> http://www.openanalytics.eu
>> 
>> ______________________________________________
>> R-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>> 
>> 
>