| Detailed description |
The package I develop (raster) has changed considerably over the past months. If someone uses version 2.7 and downloads the package with:
install.packages("raster", repos="http://R-Forge.R-project.org";)
a rather obsolete version will get installed; because builds under older versions of R are frozen.
I brought this up as a support ticket earlier, but that did not fix it for me.
http://r-forge.r-project.org/tracker/index.php?func=detail&aid=261&group_id=34&atid=194
I would prefer R-forge to not keep builds of old R versions. But I am sure others won't agree. So can you make it an option to keep, or not keep, packages build with previous versions or R?
A more refined approach, perhaps, would be to keep building the packages with one older version, or until the build fails.
|
|
