[Rcpp-devel] [External] Re: CRAN package Rcpp

[Kurt Hornik]

>>>>> Dirk Eddelbuettel writes:

> On 31 March 2026 at 11:10, luke-tierney at uiowa.edu wrote:
> | The changes in PR1466 look good. I'll use that version for my next
> | check round.

> Sounds good.

> Only one comment, just in case: PR #1466 is against current 'master', but it
> should work against the last release Rcpp 1.1.1. With a battery of recent PRs
> I didn't notice until today that the first version of #1466 was not yet
> behaving well for R older than 4.5.0, that should now be fine.

> If you apply against Rcpp 1.1.1, it should probably be Rcpp 1.1.1-1 or
> something like that in the 4.7.0/ directory of CRAN.

> I feel less certain about supporting patching R 4.6.0 now. This change
> was made March 26 -- a mere five days ago -- and given a severity of
> 'NOTE'.  Could we discuss how we may arrive at, say, an understanding
> that NOTEs are meant as heads-up with a possible and desired fix
> within the next six months, not a hot-fix rolled out a mere five days
> later?

Dirk,

Of course, this is "only a NOTE" which normally we would not ask to fix
immediately, but in the course of the next regular update.  However, as
I wrote in my original message, about 300 CRAN packages are currently
getting the R_UnboundValue NOTE via Rcpp, and their regular updates
would get blocked by this (or require additional manual processing by
the CRAN submission team).  It would really be great if this could be
avoided ...

Best
-k

> Regards, Dirk

> -- 
> dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org