From ligges at statistik.uni-dortmund.de  Sat Apr  9 19:37:50 2005
From: ligges at statistik.uni-dortmund.de (Uwe Ligges)
Date: Sat Apr  9 19:37:40 2005
Subject: Pacakge norm (was Re: [Rd] orphaning CRAN packages)
In-Reply-To: <XFMail.050409182142.Ted.Harding@nessie.mcc.ac.uk>
References: <XFMail.050409182142.Ted.Harding@nessie.mcc.ac.uk>
Message-ID: <425812EE.8090500@statistik.uni-dortmund.de>

(Ted Harding) wrote:
> On 09-Apr-05 Prof Brian Ripley wrote:
> 
>>The known problems are in the file
>>
>>http://www.r-project.org/nocvs/R.check/r-devel/norm-00check.txt
>>
>>No showstoppers, so given the saga of Ted's connectivity, I would
>>suggest waiting for the release on April 18.
>>
>>There are no declared dependencies, nor did I find any searching the 
>>code.
> 
> 
> Thanks for the pointer. Yes, they look innocuous enough.
> On the precautionary principle, however, it would be worth
> dealing with the ".Fortran" warnings, since this would
> safeguard against the possibility of name clash if some
> other package used the same names.
> 
> Question 1:
> I take it that all that's needed here is to search for
> all such calls, e.g.
> 
>   .Fortran("tobsn", ...)
> 
> and make sure that it one becomes
> 
>   .Fortran("tobsn", ... ,PACKAGE=norm)
> 
> and so on?

Yes, but PACKAGE="norm" (quotes!)


> This could be done without installing any new R (though
> being able to check against the latest would be added
> assurance), as also could be possible amendements related
> to the "Rd" warnings (which, however, only affect "help"
> and other documentation issues).
> 
> None the less,
> 
> Question 2.
> It would still be interesting to test out the compilability
> of the latest R on the machine I would be installing the
> new one on anyway (SuSE Linux 7.2 from 2001), since this
> would have oldish math libs ...
> 
> I think I have sussed out how to keep different versions
> of R on the same machine, namely:
> 
> a) Edit /usr/bin/R and change
> 
>      R_HOME_DIR=/usr/lib/R
> 
>    to
> 
>      R_HOME_DIR=/usr/lib/R-x.y.z
> 
>    as appropriate.
> 
> b) Rename the directory /usr/lib/R to /usr/lib/R-x.y.z
> 
> c) Rename /usr/bin/R to /usr/bin/R-x.y.z
> 
> d) (pro tem) Make a symbolic link
> 
>    ln -s /usr/bin/R-x.y.z /usr/bin/R


No, it is much simpler (and cleaner) to specify the installation 
directory using

   ./configure --prefix=/the/path/to/R-2.0.1

After make, make install, you can start R-2.0.1 by

   /the/path/to/R-2.0.1/bin/R


Uwe




> Then one can install a new R without thinking about it,
> provided one remembers to delete the symbolic link before
> starting (or will the new installation do this all by
> itself?).
> 
> Have I missed anything?
> 
> Thanks, and best wishes,
> Ted.


Pacakge norm (was Re: [Rd] orphaning CRAN packages)
Uwe Ligges