Skip to content
Prev 9191 / 398502 Next

update.packages() doesn't work anymore

"Michael M. Meyer" <mikem at salter-point.com> writes:
Or fix the shell script (which amounts to the same). I think this
happens when the RPM build installs in an alternate dir and later
adjusts things for the final location. A regular install has:

[pd at blueberry pd]$ R RHOME
/usr/local/lib/R
[pd at blueberry pd]$ cat `R RHOME`/bin/R
#!/bin/sh
# Shell wrapper for R executable.

R_HOME_DIR=/usr/local/lib/R
if test -n "${R_HOME}" && \
...

and no output from
[pd at blueberry pd]$ diff `which R` `R RHOME`/bin/R

We changed the use of the R_HOME environment variable recently (I
forget whether it was for 1.2.0 or 1.2.1) on the premise that the
startup script is really version dependent and good things couldn't be
expected to come from calling an old R script with a new R_HOME
setting and that R itself ought to be able to keep track of its
installation directory...

The old way probably prevented a wrong R_HOME setting in
/usr/lib/R/bin/R from having any effect. (Anyone with an older R
installed from an RPM want to try "/usr/lib/R/bin/R RHOME"?) The fix
is probably to have Martyn modify the spec file and rebuild the RPM.