Re: [R-pkg-devel] Dealing with not so temporary files

This seems to be a good occasion to note that the CRAN policy does not seem to conform the industry standards. Applications can actually store user level configuration information, cached data, logs, etc. in the user's home directory, and there standard way to do this. Here is the Apple

Re: [R-pkg-devel] Dealing with not so temporary files

Hi Gabor, That's indeed the case, but I see good reasons for the CRAN policy when we take reproducability into account. Afaik, CRAN and R always strived to provide tools that give the same output regardless of the machine they're running on when opened in a fresh R session. If packages store

Re: [R-pkg-devel] Weird error message during R CMD Check

I don’t think the suggestion below will work as it would need to be a connection string to a database that the winbuilder computer (and whatever account) that is running would have access to. It would be better to use \dontrun{} so that the examples aren’t run. This is what is done in RODBC

[R-pkg-devel] Fwd: [CRAN-pretest-archived] CRAN submission Rpolyhedra 0.2.2

Hi list: Please someone can help me with the stranges errors I recivied after a minor bugfix in my package? tests ok, devtools::check() ok, TRAVIS CI ok... What is the problem? Best, Ale. -- Forwarded message -- From: Date: 2018-03-15 1:39 GMT-03:00

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission Rpolyhedra 0.2.2

The NOTEs look harmless, the WARNING is this (InternalException (HostCannotConnect "badges.ropensci.org" [connect: failed (Connection refused (WSAECONNREFUSED))])) so badges did not want to speak to win-builder. Doesn't look like something you can deal with, except by removing the offending

Re: [R-pkg-devel] Fwd: [CRAN-pretest-archived] CRAN submission Rpolyhedra 0.2.2

On 15/03/2018 1:38 AM, alejandro baranek wrote: Hi list: Please someone can help me with the stranges errors I recivied after a minor bugfix in my package? tests ok, devtools::check() ok, TRAVIS CI ok... What is the problem? The main problem in the log is this one: * checking top-level files