Re: [R-pkg-devel] Submission to CRAN when package needs personal data (API key)

2018-09-05 Thread Duncan Murdoch
On 05/09/2018 2:20 PM, Henrik Bengtsson wrote: I take a complementary approach; I condition on, my home-made, R_TEST_ALL variable. Effectively, I do: if (as.logical(Sys.getenv("R_TEST_ALL", "FALSE"))) { ... } and set R_TEST_ALL=TRUE when I want to run that part of the test. You can also

Re: [R-pkg-devel] Submission to CRAN when package needs personal data (API key)

2018-09-05 Thread Henrik Bengtsson
I take a complementary approach; I condition on, my home-made, R_TEST_ALL variable. Effectively, I do: if (as.logical(Sys.getenv("R_TEST_ALL", "FALSE"))) { ... } and set R_TEST_ALL=TRUE when I want to run that part of the test. You can also imagine refined versions of this, e.g.

Re: [R-pkg-devel] Submission to CRAN when package needs personal data (API key)

2018-09-05 Thread Spencer Graves
On 2018-09-05 12:52, Gábor Csárdi wrote: On Wed, Sep 5, 2018 at 6:34 PM Spencer Graves wrote: The fda package disables some tests on CRAN using: if(!fda::CRAN()){ test you don't want run on CRAN } Seemingly this just checks for a couple of (5 by default) environment variables that

Re: [R-pkg-devel] Submission to CRAN when package needs personal data (API key)

2018-09-05 Thread Gábor Csárdi
On Wed, Sep 5, 2018 at 6:34 PM Spencer Graves wrote: > > The fda package disables some tests on CRAN using: > > > if(!fda::CRAN()){ > test you don't want run on CRAN > } Seemingly this just checks for a couple of (5 by default) environment variables that match "^_R_":

Re: [R-pkg-devel] Submission to CRAN when package needs personal data (API key)

2018-09-05 Thread Spencer Graves
The fda package disables some tests on CRAN using: if(!fda::CRAN()){     test you don't want run on CRAN }   I've used this in other contexts with tests that are too long to run on CRAN but that I want to run otherwise during "R CMD check".   Spencer Graves On 2018-09-05 12:13,

Re: [R-pkg-devel] Submission to CRAN when package needs personal data (API key)

2018-09-05 Thread Peter Meissner
Hey, Maybe webmockr (or something alike) can help: https://cran.r-project.org/web/packages/webmockr/index.html Best, Peter Rainer M Krug schrieb am Mi., 5. Sep. 2018, 15:38: > OK - thanks. I will than disable the checks for CRAN. > > Thanks, > > Rainer > > > > On 5 Sep 2018, at 15:37, Uwe

Re: [R-pkg-devel] Submission to CRAN when package needs personal data (API key)

2018-09-05 Thread Rainer M Krug
OK - thanks. I will than disable the checks for CRAN. Thanks, Rainer > On 5 Sep 2018, at 15:37, Uwe Ligges wrote: > > You should not run on CRAN. Note that the checks are done almost daily oin > several platforms, hence the API key is used for about 10 check runs a day. > > Best, > Uwe

Re: [R-pkg-devel] Submission to CRAN when package needs personal data (API key)

2018-09-05 Thread Uwe Ligges
You should not run on CRAN. Note that the checks are done almost daily oin several platforms, hence the API key is used for about 10 check runs a day. Best, Uwe Ligges On 05.09.2018 09:28, Rainer Krug wrote: Hi I have a package at GitHub (https://github.com/rkrug/ROriginStamp) which I am

[R-pkg-devel] Submission to CRAN when package needs personal data (API key)

2018-09-05 Thread Rainer Krug
Hi I have a package at GitHub (https://github.com/rkrug/ROriginStamp) which I am pre[paring for CRAN. It creates a trusted timestamp using the API fro OriginStamp (https://originstamp.org/home) which requires an API key. Now this API should not be made public, as to much traffic through one