R help - Mar 2008 - smoothest way to upgrade R, say from 2.6.1 to 2.6.2?

Like many software assemblies, R is updated frequently.  Also, it
creates its own release-numbered directory when it is installed.
Packages get dumped into the subdirectory "library".  I have a
personal
habit of storing documents related to R packages in the "doc"
subdirectory.

Here are my questions.

(1) How do people manage an upgrade, from 2.6.1, say, to 2.6.2?  2.6.2
will create its own subdirectory, obliging a copy of library contents to
the new spot.  The documents are easier. 

(2) The problem with simply copying library contents is a fear of upward
incompatibilities.  Am I worrying for naught here?  Are packages upward
compatible but possibly not downwardly so?

(3) What about changing shortcuts, places for .Rprofile and the like?
Do people have scripts that do all these things at once?  

It would be nice to have a single control file where R binaries and
libraries and the like could be specified.  That way, all that would
need to be done is edit one file with an uptick on a point release
number, say, and things would be fine.   I suggest this because R is so
rich and deep that there may well be such a thing I just don't know
about.  Or there may be a way of arranging things so they are done this
way.

Ideas?

  -- Jan



	[[alternative HTML version deleted]]

On Thursday 13 March 2008 06:05:15 pm Galkowski, Jan wrote:
GJ> (1) How do people manage an upgrade, from 2.6.1, say, to 2.6.2?  2.6.2
GJ> will create its own subdirectory, obliging a copy of library contents to
GJ> the new spot.  The documents are easier.

You forgot to enlighten us about your system. From what you are telling I 
would guess its Windows (XP?). On my windows machine I install R in the very 
same directory of the old R. So you could create programs/R and there install 
your R but of course you must then alternate the suggested directory during 
the installation.

GJ>
GJ> (2) The problem with simply copying library contents is a fear of upward
GJ> incompatibilities.  Am I worrying for naught here?  Are packages upward
GJ> compatible but possibly not downwardly so?

There is no problem within minor releases like 2.6.1 -> 2.6.2 but on 
greater "jumps" update.packages offers the option checkbuilt which if
set
TRUE updates the packages to their next built. So if 2.7.0 is released and 
you install that are over your old you should enable this option.


GJ> (3) What about changing shortcuts, places for .Rprofile and the like?
GJ> Do people have scripts that do all these things at once?

See above

GJ>
GJ> It would be nice to have a single control file where R binaries and
GJ> libraries and the like could be specified.  That way, all that would
GJ> need to be done is edit one file with an uptick on a point release
GJ> number, say, and things would be fine.   

I don't think this is necessary.

Cheers
Stefan



-- 
Microeconomics
University of Erfurt