The latest R-2.5.0 release comes with a new "Rscript" tool which will automatically be installed as /usr/bin/Rscript. However, due to the sandbox compilation the Rscript tools doesn't work properly as it tries to call the main 'R' executable with an incorrect path. Reproducible: Always Steps to Reproduce: 1. run "Rscript --verbose test.R" and see output Actual Results: running '/var/tmp/portage/dev-lang/R-2.5.0/image//usr/lib64/R/bin/R --slave --no-restore --file=blah.R' Rscript execution error: No such file or directory Expected Results: The output should show "/usr/bin/R --slave --no-restore" instead Of course, due to the incorrect path, the whole Rscript binary is useless and doesn't work as expected.
Hi Jens, Thanks for your bug report! I believe I just fixed this in portage cvs. Please re-sync in an hour or so and let me know if it works. Thanks, Markus
This one should be fixed, I think ... closing. THanks, Markus