GOOD NEWS AND BAD NEWS:
* First the good news: I heard from Brian Ripley; see below.
His web site says, "He retired in August 2014 on grounds of ill health."
(http://www.stats.ox.ac.uk/~ripley/) I was pleased to see that he seems
to be well enough to send me the email
On Thu, 23 Jan 2020 at 02:49, Spencer Graves
> Hello, All:
> GOOD NEWS AND BAD NEWS:
>* First the good news: I heard from Brian Ripley; see below.
> His web site says, "He retired in August 2014 on grounds of ill health."
> (http://www.stats.ox.ac.uk/~ripley/) I was
I think that message means what it says, and I read it as pretty
straightforward and business like. The issue is not web scraping. There are
two errors here:
1. You can not write to the user's space without first explicitly asking
permission of the user. The suggested policy
I'm trying to repackage an R function so I can update the licence. I'm stuck
with the automatic checks. The problem appears to be the following three NOTEs
in the checking output:
* checking CRAN incoming feasibility ... NOTE
Maintainer: ‘Ian Walker <
On Wed, 22 Jan 2020 10:29:51 +
Ian Walker wrote:
> * checking CRAN incoming feasibility ... NOTE
> Maintainer: ‘Ian Walker <
This NOTE is there for CRAN staff to have another look at the
Maintainer: field in case this is someone's first submission or
Just to close one loop here:
On 15 January 2020 at 16:53, Dirk Eddelbuettel wrote:
| Rocker should be building weekly r-devel and drd (similar, was meant to be a
| littler "lighter", effectively the same) images.
| As Merlise noticed, somehow the cronjob push to the Docker Hub build service
(a) Spelling issues: False positive are checked manually by CRAN, so just tell
them on submission. For software items, Uwe at some point recommended "Single
quotes around software names such as 'pkg', functions should be written with
parentheses as in foo()."
(b) The procedure for submitting
Source packages may not contain any form of binary executable code.
On Wed, Jan 22, 2020 at 3:54 PM Jonathan Greenberg wrote:
> What is the policy on adding Windows executables to an R package? My
> gdalUtils package
What is the policy on adding Windows executables to an R package? My gdalUtils
package could REALLY use this ability (right now it requires users to manually
install GDAL which can cause headaches for folks). Related: what about
Are there reasonable tutorials
PS I don't know if you would be allowed to include a utility function
to be run manually by users after setup that would download binaries
from a trusted source and put them in an appropriate/findable place on
the user's system.
On Wed, Jan 22, 2020 at 4:06 PM Ben Bolker wrote:
Mail list logo