[R-pkg-devel] Examples for functions called by Shiny server

I have been asked to provide examples within the Rd files of my package (github.com/rmsharp/nprcgenekeepr ) by the CRAN package reviewer. I have to export those functions called by the server.R script (or use ::: notation), which in turn generates an Rd f

Re: [R-pkg-devel] packaging biosig for R

I suspect the question in this case depends on the availability of libbiosig. If CRAN test machines don't have that and its source isn't included in the R package, then it will fail on initial install. CRAN doesn't have a lot of resources to install difficult libraries; I have no idea if that

[R-pkg-devel] Warning in dir.create(vd2 <- "vign_test"): 'vign_test' already exists

Hello, All:   Under Windows 10, "R CMD check sos_2.0-1.tar.gz" cloned from "https://github.com/sbgraves237/sos"; ends with: * checking rebuild of vignettes outputs ...Warning in dir.create(vd2 <- "vign_test"):  'vign_test' already exists   Under macOS 10.15.3 it finishes fine.

Re: [R-pkg-devel] packaging biosig for R

I am just a lurker (not representing CRAN) but I am having a hard time understanding your question. Binary packages are a convenience for users, not a method for submitting packages. When you have an R package accepted it is accepted in source format. If it doesn't exclude support for Windows or

[R-pkg-devel] packaging biosig for R

Dear R packagers, the Biosig project [1] supports reading of about 50 different data format [2]. Recently, a language binding to R was added, because a user of Biosig asked for it.  I've read the policy [3], and it seems the biosig would qualify as binary package. The underlying library (libb