On Mon, 2009-04-06 at 16:09 +0200, Martyn Plummer wrote: > This is using the JRI interface to call the R engine from within java. > If you want to do this then you should write a wrapper script that sets > all the necessary environment variables, the class path and so on. > > The rJava package contains two examples "rtest" and "rtest2", both of > which are installed, along with a wrapper script called "run". Yes and their first step is: > #!/bin/sh > > R_HOME=/usr/lib64/R even before running anything > A more extensive example is the JGR package which provides a Java GUI > for R. The GUI can be launched from the shell by running a wrapper > script - again called "run" - which is installed with the JGR package. > This script also works perfectly for me. > > This is not a reason to set R_HOME globally, I see two points, either we help the user by setting the R_HOME ourself directly within R and rjava works directly or we do not and let set R_HOME which he will do anyway to make rjava working... Is there not a way for the testing suite of the development version to test if R_HOME is already set ? Another solution could be to add the R_HOME only on the rjava package. If nothing is acceptable then we should roll back, I don't want to break R :) Best regards, Pierre _______________________________________________ Fedora-r-devel-list mailing list Fedora-r-devel-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-r-devel-list
