FYI, based on my experiences today:
- I am installing the R-4-0 branch from svn today (march 31)
- I am using clang8 on OS X as recommended by CRAN/Simon
- I am using homebrew, a widely used package manager on OS X, for many of
my dependencies
1. Before installing R-4-0 I updated homebrew to
We are now at Rcpp 1.0.4.4 on master and in the drat -- Mattias Ellert
contributed _another_ cleanup PR on the recent exceptions refactoring PR
fixing two overlooked aspects that came up at ROOT.
As before, master is current and the corresponding tar.gz is at the drat:
install.packages("Rcpp"
As CRAN told me this morning, BioConductor upgraded the GoSemSim package. So
CRAN no longer exeriences any breakage related to the 1.0.4 release, and sees
no need for an immediate patch release. Neither do I.
For those bitten by whatever failings that revealed itself only outside the
test matrix
On 18 March 2020 at 10:48, Davis Vaughan wrote:
| Here is the list of failures from my partial test. Notably (at least to
| me), are dplyr and bigmemory.
Two days later. Neither one is failing at CRAN:
https://cloud.r-project.org/web/checks/check_results_bigmemory.html
https://cloud.r-projec
Follow up of
http://lists.r-forge.r-project.org/pipermail/rcpp-devel/2020-March/010411.html
.
I am on a macOS running Mojave, 10.14.5.
I ran a partial set of revdeps for Rcpp (in alphabetical order), and 39 out
of 546 fail with CRAN Rcpp on macOS because of the following issue, fixed
in Rcpp deve
