Jan Theodore Galkowski
2010-Jan-17 15:33 UTC
[Rd] packages built against upcoming releases
I admire package-builders being proactive and having their facilities ready for upcoming R releases. However, if the publicly released version of R is 2.10.1 and a package is built for R 2.11.0, users get the embarrassing notice about a disconnect, and cannot do much about it. If it is tedious to roll out a new package on time, perhaps there's a possibility for automation here. Thanks. I encountered this yesterday with RHmm. I'm running R on WinXP. Happy R user! - Jan Galkowski.
On 17.01.2010 16:33, Jan Theodore Galkowski wrote:> I admire package-builders being proactive and having their facilities > ready for upcoming R releases. However, if the publicly released > version of R is 2.10.1 and a package is built for R 2.11.0, users get > the embarrassing notice about a disconnect,What a disconnect?> and cannot do much about it.They should install the version that is intended for R-2.10.x releases, not the one for the development version. The RHmm version in the 2.10 repository in CRAN has Built: R 2.10.1; i386-pc-mingw32; 2010-01-03 15:59:39 UTC; windows hence built with R-2.10.x as required.> If it is tedious to roll out a new package on time, perhaps there's a > possibility for automation here.It is automated and we are currently building for R-2.9.x, R-2.10.x and R-devel (the latter in 32-bit and 64-bit), and you have just to say install.packages() and your R wil grab the right version. I suspect you downloaded something manually from the wrong repository. Uwe Ligges> Thanks. I encountered this yesterday with RHmm. I'm running R on > WinXP. > > Happy R user! > > - Jan Galkowski. > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel