Hi, I am preparing a new package r2sundials for submission to cran. It depends on third part software (https://computing.llnl.gov/projects/sundials). This will be my first submission of the kind so I am wondering how it is supposed to be tested so that I can reliably check the box "tested on R-devel" during submission process? I suppose that sundials is not installed on windev. And even if it was, I need a particular option in this software (index size set to 32 bits) which is probably not activated in the hypothetical installation. So I cannot use win-builder.r-project.org. Am I supposed to install current r-devel version and test my package on it locally? And another question. Recently, I had to fix many LTO (link time optimization) related issues in a third part software included in one of my old packages. Have I to test with LTO activated the new package too given that it is _not_ included in the package ? Thanks to share your experience and wisdom. Best, Serguei.
[R-pkg-devel] third part software dependency
6 messages · Dirk Eddelbuettel, Ralf Stubner, Serguei Sokol
On 30 August 2019 at 11:10, Serguei Sokol wrote:
| I am preparing a new package r2sundials for submission to cran. It | depends on third part software | (https://computing.llnl.gov/projects/sundials). This will be my first | submission of the kind so I am wondering how it is supposed to be tested | so that I can reliably check the box "tested on R-devel" during | submission process? | I suppose that sundials is not installed on windev. And even if it was, | I need a particular option in this software (index size set to 32 bits) | which is probably not activated in the hypothetical installation. So I | cannot use win-builder.r-project.org. | Am I supposed to install current r-devel version and test my package on | it locally? The builder.r-hub.io service is a good alternative. It offers twelve different platforms, including a few r-devel ones. That said, it won't have sundials either so you may have to pull sundials in during configure or via Make dependencies or ... Dirk
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
On 30 August 2019 at 07:24, Dirk Eddelbuettel wrote:
|
| On 30 August 2019 at 11:10, Serguei Sokol wrote:
| | I am preparing a new package r2sundials for submission to cran. It | | depends on third part software | | (https://computing.llnl.gov/projects/sundials). This will be my first | | submission of the kind so I am wondering how it is supposed to be tested | | so that I can reliably check the box "tested on R-devel" during | | submission process? | | I suppose that sundials is not installed on windev. And even if it was, | | I need a particular option in this software (index size set to 32 bits) | | which is probably not activated in the hypothetical installation. So I | | cannot use win-builder.r-project.org. | | Am I supposed to install current r-devel version and test my package on | | it locally? | | The builder.r-hub.io service is a good alternative. It offers twelve | different platforms, including a few r-devel ones. | | That said, it won't have sundials either so you may have to pull sundials in | during configure or via Make dependencies or ... An alternative is of course to use a Docker image. I have long provided two different containers within the Rocker Project that have r-devel (to be invoked as RD). You can pretty easily fire up the container, install sundials and then save it again locally. Ask me off-line about how if you need help. Or, of course, do as I and many others do and just keep a local r-devel build in /usr/local .... Dirk
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
On Fri, Aug 30, 2019 at 11:10 AM Serguei Sokol <serguei.sokol at gmail.com> wrote:
I am preparing a new package r2sundials for submission to cran. It depends on third part software (https://computing.llnl.gov/projects/sundials).
Are you aware of the sundialr package? https://cran.r-project.org/package=sundialr
This will be my first submission of the kind so I am wondering how it is supposed to be tested so that I can reliably check the box "tested on R-devel" during submission process? I suppose that sundials is not installed on windev. And even if it was, I need a particular option in this software (index size set to 32 bits) which is probably not activated in the hypothetical installation. So I cannot use win-builder.r-project.org. Am I supposed to install current r-devel version and test my package on it locally?
Besides Dirk's suggestions, you can also use a CI service like Travis. there you can install additional dependencies before testing the package itself. However, the question remains how CRAN will test the package without having sundials installed. cheerio ralf
Hi Ralf,
On 30/08/2019 16:04, Ralf Stubner wrote:
On Fri, Aug 30, 2019 at 11:10 AM Serguei Sokol <serguei.sokol at gmail.com> wrote:
I am preparing a new package r2sundials for submission to cran. It depends on third part software (https://computing.llnl.gov/projects/sundials).
Are you aware of the sundialr package? https://cran.r-project.org/package=sundialr
Yes, I do. I explain why I created a new package in Readme.md visible here https://github.com/sgsokol/r2sundials
This will be my first submission of the kind so I am wondering how it is supposed to be tested so that I can reliably check the box "tested on R-devel" during submission process? I suppose that sundials is not installed on windev. And even if it was, I need a particular option in this software (index size set to 32 bits) which is probably not activated in the hypothetical installation. So I cannot use win-builder.r-project.org. Am I supposed to install current r-devel version and test my package on it locally?
Besides Dirk's suggestions, you can also use a CI service like Travis. there you can install additional dependencies before testing the package itself.
Thanks for suggestion but I don't use Travis. Until now I didn't need it. Locally, I installed sundials/cvodes and my package. That's enough for the tests.
However, the question remains how CRAN will test the package without having sundials installed.
Right. Best, Serguei.
On 30/08/2019 15:58, Dirk Eddelbuettel wrote:
On 30 August 2019 at 07:24, Dirk Eddelbuettel wrote: | | On 30 August 2019 at 11:10, Serguei Sokol wrote: | | I am preparing a new package r2sundials for submission to cran. It | | depends on third part software | | (https://computing.llnl.gov/projects/sundials). This will be my first | | submission of the kind so I am wondering how it is supposed to be tested | | so that I can reliably check the box "tested on R-devel" during | | submission process? | | I suppose that sundials is not installed on windev. And even if it was, | | I need a particular option in this software (index size set to 32 bits) | | which is probably not activated in the hypothetical installation. So I | | cannot use win-builder.r-project.org. | | Am I supposed to install current r-devel version and test my package on | | it locally? | | The builder.r-hub.io service is a good alternative. It offers twelve | different platforms, including a few r-devel ones. | | That said, it won't have sundials either so you may have to pull sundials in | during configure or via Make dependencies or ... An alternative is of course to use a Docker image. I have long provided two different containers within the Rocker Project that have r-devel (to be invoked as RD). You can pretty easily fire up the container, install sundials and then save it again locally. Ask me off-line about how if you need help. Or, of course, do as I and many others do and just keep a local r-devel build in /usr/local ....
Thank Dirk. This was my spare option and I think this is what I'll do.