From erich.neuwirth at univie.ac.at  Thu Dec 25 12:21:59 2008
From: erich.neuwirth at univie.ac.at (Erich Neuwirth)
Date: Thu, 25 Dec 2008 12:21:59 +0100
Subject: [Rd] rscproxy version conflict
In-Reply-To: <B291D293-23F7-4095-95EF-3C48525EB603@r-project.org>
References: <405593F1A35DDD11B2B4000C29F5CF53034642@exchange-server.ow.ks>
	<B291D293-23F7-4095-95EF-3C48525EB603@r-project.org>
Message-ID: <49536CD7.5030502@univie.ac.at>



Simon Urbanek wrote:
> 
> It's ok to use a package built for 2.8.0 in 2.8.1 but not vice versa. It
> is rare, but it has happened before that a bugfix or visibility change
> adds a symbol in x.y.1 that was not there in x.y.0. Then if your package
> checks for that particular feature and uses it you cannot use that
> binary with x.y.0. Again, this is rather rare and you as the package
> author know about it, but to be on the safe side I was recommending
> against that. However, as Brian pointed out this happens far more often
> on the R function level than on the C API level.
> 
> (I know about this DLL version check because it was the first change I
> made to JRI since I wasn't willing to release Windows binary some five
> times a year ;)).
> 

What happened recently was that R still officially was at 2.8.0,
but the binary Windows packages already were compiled with
RC1 of 2.8.1. So by downloading the official versions of R
and then some packages from CRAN one had a mixture of old R and new
packages which is what you describe as "this should not be done".







-- 
Erich Neuwirth, University of Vienna
Faculty of Computer Science
Computer Supported Didactics Working Group
Visit our SunSITE at http://sunsite.univie.ac.at
Phone: +43-1-4277-39464 Fax: +43-1-4277-39459



[Rd] rscproxy version conflict
Erich Neuwirth