search for: _r_check_have_mysql_

...even though I have "BuildVignettes: false" in the DESCRIPTION file. What is the mechanism for indicating that CRAN should not attempt to check this code? Perhaps it is intentionally difficult - I can see an argument for that. (For running tests there are environment variables, e.g._R_CHECK_HAVE_MYSQL_, but using these really clutters up a vignette, and it did not seem necessary to use them before.) (The difficult also occurs on R-forge, possibly because it is using --as-cran like settings.) Paul

Is there a good strategy for testing examples which should not be run by default? For instance, I have examples which get data from the Internet. If I wrap them in try() then they can be skipped if the Internet is not available, but may not be tested in cases when I would like to know about the failure. (Not to mention that the example syntax is ugly.) If I mark them \dontrun or \donttest