[R-pkg-devel] Advice for addressing CRAN rejection
smallepsilon
@m@||ep@||on @end|ng |rom proton@me
Wed May 14 22:41:27 CEST 2025
On Wednesday, May 14th, 2025 at 12:59 PM, Ben Bolker <bbolker using gmail.com> wrote:
>
>
> On Wed, May 14, 2025 at 12:46 PM Dirk Eddelbuettel edd using debian.org wrote:
>
> > [ If you could, please set your email software up such that posts to a
> > mailing lists are not signed, it makes reading them more cumbersome. It
> > also means I can't reply (easily) inline now. ]
> >
> > In most cases environment variables need to be set before the process
> > starts. Setting them inside the running R process likely has no effect.
>
>
> That's what I thought, although it means then (I assume) that you
> have to rely on whatever settings CRAN has determined for its testing
> platforms. The RhpcBLASctl package
> https://CRAN.R-project.org/package=RhpcBLASctl can do some of these
> settings within a running R process, I don't know if it does what you
> need or not.
Thanks for the package reference. The description is promising, but using it still resulted in non-identical objects.
All of this leads me to think that the lack of control over the CRAN platforms and the difficulty (if not impossibility) of testing what I want to test mean that it is reasonable to remove my attempts to test it from the package that I upload to CRAN. Thoughts?
More information about the R-package-devel
mailing list