It's really odd that people blog about their own inefficient scripts
rather than read the R documentation.
Because this scripts checks (very inefficiently) if a package is
already installed, it would not solve the problem discussed in this
thread. And install.packages() takes a vector of
Simon,
That's a better way, indeed. I had missed your previous post, so thank you
for reposting. My original motivation for the script was to sync certain
core packages across multiple machines, but it works well for upgrades,
too. The script also provides a means of weeding out my library by not
Well, that's a bit convoluted way (I really don't see the point of that
script) - if you want to re-install packages across R versions (not the topic
of this thread!) it is far easier than that and I posted it here just a few
days ago:
# for packages from user location:
Brian,
Since the problem was fixed by updating packages with checkBuilt=T, wouldn't
installing packages fresh using the script have avoided the problem?
Perhaps section 2.8 of the Windows FAQ should be incorporated into the Mac
FAQ? The checkBuilt trick is otherwise not brought to our attention.
On 25/05/2011, at 12:19 PM, Simon Urbanek wrote:
Normally you just install new R and then use Package Manager to install
packages to match your previous version. If you blow away old R, you will
have no track of packages you installed before.
I've been in the habit of keeping all the .tgz
On Wed, May 25, 2011 at 11:50, Prof Brian Ripley rip...@stats.ox.ac.ukwrote:
On Wed, 25 May 2011, Tom Hopper wrote:
Brian,
Since the problem was fixed by updating packages with checkBuilt=T,
wouldn't
installing packages fresh using the script have avoided the problem?
No, because it
On May 25, 2011, at 7:17 AM, Tom Hopper wrote:
On Wed, May 25, 2011 at 11:50, Prof Brian Ripley rip...@stats.ox.ac.ukwrote:
On Wed, 25 May 2011, Tom Hopper wrote:
Brian,
Since the problem was fixed by updating packages with checkBuilt=T,
wouldn't
installing packages fresh using the
On Wed, May 25, 2011 at 15:23, Simon Urbanek simon.urba...@r-project.orgwrote:
On May 25, 2011, at 7:17 AM, Tom Hopper wrote:
On Wed, May 25, 2011 at 11:50, Prof Brian Ripley rip...@stats.ox.ac.uk
wrote:
On Wed, 25 May 2011, Tom Hopper wrote:
Brian,
Since the problem was fixed
On Wed, May 25, 2011 at 9:52 AM, Tom Hopper tomhop...@gmail.com wrote:
On Wed, May 25, 2011 at 15:23, Simon Urbanek
simon.urba...@r-project.orgwrote:
On May 25, 2011, at 7:17 AM, Tom Hopper wrote:
On Wed, May 25, 2011 at 11:50, Prof Brian Ripley rip...@stats.ox.ac.uk
wrote:
On Wed,
On Wed, May 25, 2011 at 15:57, Sean Davis sdav...@mail.nih.gov wrote:
On Wed, May 25, 2011 at 9:52 AM, Tom Hopper tomhop...@gmail.com wrote:
snip
understand this well enough so that I can avoid similar problems. If I
install a new version of R and then, without doing anything else, either
Just wanted to mention that I saw the same behavior with a package or
two, and found the same workaround (copying libs to the 2.12 tree).
Carl
quote
Message: 4
Date: Tue, 24 May 2011 16:32:41 +1000
From: Ian Reeve ire...@une.edu.au
To: r-sig-mac@r-project.org r-sig-mac@r-project.org
Subject:
Ian,
I agree with Brian. I checked the CRAN binaries of class and deldir and they
are correctly linking to 2.13, so I suspect you have old packages in your tree.
I don't think this can happen with stock R binary, it seems that at some point
you moved packages or there is/was a symlink between
Thanks Brian and Simon for the suggestions.
update.packages(checkBuilt=TRUE)
fixed the load problem and all the functions I was using in R 2.12 are running
identically in R 2.13.0.
For future reference, when I update to a new version of R, is it good practice
to:
sudo rm -rf
There's a handy script to automate the update process that I came across
some time ago at
https://bridgewater.wordpress.com/2010/12/21/my-favorite-r-packages-installed-with-one-command/
When you run the script, it will automatically install the libraries that
you set up in the script. When you
14 matches
Mail list logo
