Option "installWithVers" seems to impact new.packages() badly?
Also, I don't know what this has to do with BioC. This is core R, so pertinent to this list. Otherwise, perhaps it should be taken out?
On 10/4/05, A.J. Rossini <blindglobe at gmail.com> wrote:
I expect "new.packages()" to not report on packages which I've installed, as per documentation. best, -tony On 10/4/05, Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote:
Hard to know what you expect here. There is no recent change that I can see. I removed ash and then installed it with version. new.packages() showed it as new in both 2.1.1 and 2.2.0-beta. The issue is that installed.packages() has never been taught about versioned installs, and you might like to take that up with your BioC colleagues who added the idea. On Fri, 30 Sep 2005, A.J. Rossini wrote:
In Rdevel, SVN version built this morning around 10am central european time, it looks like install.packages(new.packages(),installWithVers=TRUE) seem to ignore the version information -- that is, it reinstalls current versions of packages.
I believe it always did: it certainly does in 2.1.1 for me.
This did not happen before I used "installWithVers=TRUE" option, that is I could use update.packages() and install.packages(new.packages()) to keep a current, platform-complete, installed base of CRAN.
-- Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595
-- best, -tony blindglobe at gmail.com Muttenz, Switzerland. "Commit early,commit often, and commit in a repository from which we can easily roll-back your mistakes" (AJR, 4Jan05).
-- best, -tony blindglobe at gmail.com Muttenz, Switzerland. "Commit early,commit often, and commit in a repository from which we can easily roll-back your mistakes" (AJR, 4Jan05).