Hey Rich, thank you for your response.
In my case, I explained the reasoning to justify the
USA.state.boundaries package being over 5 MB and why it is needed by
iemisc, including providing previous e-mail discussions between Uwe and
myself, on the various re-submittals of the
Ben, thank you for your response.
The text2sdg package was added on 24 January 2023.
I had created a drat repository called USA.state.boundaries.data to
store the full set of maps (1 of which is needed for my iemisc package)
and I had only a subset of the maps in the USA.state.boundaries
For closure, I was advised by Professor Ripley to both pass
"-std=f008" in Makevars and add "SystemRequirements: A version of
gfortran supporting Fortran 2008" to the DESCRIPTION. CRAN accepted
the package with those two changes. I also note that the R Daily News
of 2023-02-03 [1] has the
checking whether package ‘epanet2toolkit’ can be installed ... WARNING
Found the following significant warnings:
report.c:1466:37: warning: argument to ‘sizeof’ in ‘snprintf’ call is the
same expression as the destination; did you mean to provide an explicit
length? [-Wsizeof-pointer-memaccess]
On 03/02/2023 12:00 p.m., John P. Nolan wrote:
Dear R-package-devel,
I am updating package mvmesh that is on CRAN. I would like to split that
package into two parts, mvmesh (multivariate meshes/grids) and mvhist
(multivariate histograms). Does CRAN have a policy/practice on this? I did a
Dear R-package-devel,
I am updating package mvmesh that is on CRAN. I would like to split that
package into two parts, mvmesh (multivariate meshes/grids) and mvhist
(multivariate histograms). Does CRAN have a policy/practice on this? I did a
search, but found nothing on this.
I would do
Dear List -
What’s the latest best practice on trying to reproduce warnings raised
on CRAN checks?
I updated my epanet2toolkit package earlier this week.
R CMD check —as-cran was clean on RHUB and Winbuilder and my local
machines. But on CRAN a few variations are causing warnings.
For example
On 02/02/2023 7:24 p.m., Simon Urbanek wrote:
Duncan,
I don't know if it is best, but you can have a look at "background"[1] which is I believe
what "later" was inspired by. It is a very minimal example so should give you ideas on
how to do that in your package - it runs the R code on the
