On Mon, 26 Apr 2010, Marshall Feldman wrote:
So why not have the appropriate
scripts ask a few questions upon the first installation of R (e.g., "Do you
want to configure R with a "global" library for packages to make future
upgrading easier?") and at upgrade time ("Your previous version of R
I think it makes more sense for most users to have a global library
(as you call it), rather than put the library under the current
installation. I have been doing that for years, and it saves a lot of
trouble.
When I have helped people learn R, the need to copy the library when
updating is a reg
On 4/25/2010 19:39:52, Tal Galili wrote:
*c) R core implementation ?!*
I hope I am not being rude (or jumping into any open doors) in asking this
but...
What do you think about implementing this strategy into the R basic
installation?
Tal,
As a general rule, I think R should make upgradi
Hi Daniel,
Thanks for taking the time to go through this.
You wrote:
> "I don't see the advantage over using the R_LIBS environment variable"
You are correct - there is no advantage *over *doing that, because that is *
exactly* what my code is doing :)
You wrote:
> You need to initially copy
> -Original Message-
> From: r-help-boun...@r-project.org [mailto:r-help-boun...@r-project.org]
> On Behalf Of Tal Galili
> Sent: Sunday, April 25, 2010 9:40 AM
> To: r-help@r-project.org
> Subject: [R] Upgrading R using the "global library folder" strategy -
Hello dear R-help mailing list,
The other day I published a blog post (with some R code) to help R-users who
want to implement a simpler upgrading strategy for R (under windows - but
probably the same will be true of mac OS, I am not sure about Linux).
This e-mail has 3 goals: (a) To share, (b) t
6 matches
Mail list logo
