Hi Spencer,
I remember having a similar error a few years ago when trying to compile R (and
its recommended packages, e.g. mgcv) from source. I was using clang as a
compiler (this is what Hadley recommends in his book "R packages"), and I
solved the issue by going back to g++. This can be done
The NOTE refers to Makevars and Makevars.win. The most logical place to start
your investigation would be those two files. Do you have any reason to believe
that they are *not* the culprits?
Max
From: R-package-devel on behalf of
Jarrett Phillips
Sent: April 1
Hi Bill,
Maybe I'm missing something, but if RcppEigen were the cause of the NOTE,
wouldn't RcppEigen also get the same NOTE? However, it does not:
https://cran.r-project.org/web/checks/check_results_RcppEigen.html
And for what it's worth, neither does BH:
https://cran.r-project.org/web/checks
Looking at `tools::CRAN_package_db()`, I can see 1433 packages that mention R
in the Description field, and only 77 use single quotes around it. So I would
say that the consensus seems to be to *not* use single quotes.
On the other hand, I am not convinced you need to mention R at all in your
D
Hi David,
Non-staged installation is something new in R-devel:
https://developer.r-project.org/Blog/public/2019/02/14/staged-install/index.html
Package maintainers can opt out of it (through DESCRIPTION), and I'm assuming
CRAN wants a quick way to know if that was the case when diagnosing a
su
Hi John,
I think you misread the check output. You got a WARNING because you didn't
change the package version (the current 0.1.0 is the same as the incoming
0.1.0). At the end of the output, you also get the results of R CMD check on
the current version (i.e. the one on CRAN). Of course, the
hat.
Max
From: Rami Krispin
Sent: February 7, 2018 1:49:34 PM
To: Maxime Turgeon
Cc: Uwe Ligges; r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Depreciate Function
I follow the example of the R Packages book about depreciating a function which
can be find here:
http://r-pkgs
Hi Rami,
Is there a reason for still using the deprecated functions in your examples?
Because that's what's triggering the warnings.
Best,
Max
From: R-package-devel on behalf of Rami
Krispin
Sent: February 7, 2018 1:32:37 PM
To: Uwe Ligges
Cc: r-package-de
Hi Jorge,
All the Rd files are available to users if they download the source code. They
are also available through the CRAN mirror on Github (github.com/cran). In
other words, you shouldn't put personal information in the help files, even if
you use the 'dontshow' macro.
Max
__
Hi Jernej,
The check errors you get are for older releases of R (3.3.2 and 3.3.3). The
issue arises from your requirement in DESCRIPTION that the version of stats
should be 3.4.0. Therefore, the solution to your problem depends on whether you
really need this requirement on the version of stat
This is well documented in Writing R extensions:
- https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Printing for
I/O streams
-
https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Registering-native-routines
for native routine registrations.
As for the random number gen
If you look at the CRAN page for the package doMC, you'll notice that in the
reverse dependencies, there are only "reverse suggests" and "reverse enhances"
(no "reverse depends"). Looking at the source code for some of the packages in
"reverse suggests" should give you an answer to your question
12 matches
Mail list logo
