We all love R CMD check. :) In my opinion it would be even better if it had options to - Run all checks, even if one fails with an error. I realize this sometimes might not make sense (e.g. if there is no DESCRIPTION file), but often does. - Run all examples even if an example fails. I think it would be great to get all failing examples at once, so that a package author can estimate the amount of breakage. Thank you for considering there, Gabor
Two ideas / feature requests for R CMD check
2 messages · Gábor Csárdi, Mohit Dayal
Hi All, One thing that I've encountered with R CMD check is that if your package uses some functions from a base package, then the corresponding NAMESPACE imports do not seem to be automatically suggested. It might possibly an issue with how one's system is configured, but say, with the --as-cran switch this thing should be picked up on. Like I felt this was something else that could be looked into :) Thanks! Mohit ------ mohitdayal.strikingly.com ---------- Forwarded message ---------- From: G?bor Cs?rdi <csardi.gabor at gmail.com> Date: 25 February 2016 at 05:40 Subject: [Rd] Two ideas / feature requests for R CMD check To: "r-devel at r-project.org" <r-devel at r-project.org> We all love R CMD check. :) In my opinion it would be even better if it had options to - Run all checks, even if one fails with an error. I realize this sometimes might not make sense (e.g. if there is no DESCRIPTION file), but often does. - Run all examples even if an example fails. I think it would be great to get all failing examples at once, so that a package author can estimate the amount of breakage. Thank you for considering there, Gabor ______________________________________________ R-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel