Just went running on the snowy streets and had one good thought related to:
On 10 December 2005 at 09:44, Dirk Eddelbuettel wrote: | | On 10 December 2005 at 16:23, Egon Willighagen wrote: | | *: I think the R CMD INSTALL might actually do some checking? | | It is R CMD CHECK, which we automatically invoked on the (core) packages that | r-recommended depends on ... and had to disable as some the tests are too These are _source_ level checks ensuring that the CRAN source package is internally consistent, has documentation, builds, runs its examples etc pp. What we really need is a _binary_ level check for each autobuilt package as probably few of these autobuilt packages are going to be tested manually by us. So a robot has to do it. In particular, this would check that the package -- installs, ie has correctly specified Depends: -- loads, and ie has sufficient Depends: -- runs its examples to check it is as it should be If that was part of a cron job, then identifying which new packages need to be pulled and billed and which old binaries can be removed is the easy part. Thoughts? Dirk -- Hell, there are no rules here - we're trying to accomplish something. -- Thomas A. Edison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]