[R-pkg-devel] Properly referencing copied code

2024-07-11 Thread DRC via R-package-devel
I'm trying to submit a package to CRAN that uses external C libs but properly crediting copyright holders and authors is the main issue holding up the submission and I've repeatedly failed to satisfy the requirements. I am having a lot of trouble understanding what/who I need to be listing in my

Re: [R-pkg-devel] Options "reset" when options(opts)

2024-07-11 Thread Vladimir Dergachev
On Thu, 11 Jul 2024, David Hugh-Jones wrote: This surprised me, even though it shouldn’t have done. (My false internal model of the world was that oo <- options(); … options(oo) would overwrite the entire options list with the old values.) I wonder if it would be worth pointing out explicitly

Re: [R-pkg-devel] Help for understanding CRAN rejection

2024-07-11 Thread Matei Teleman
Dear Ivan, Thank you so much for your help. I followed your advices and I reduced the size of the example data, move one package from Import to Suggest. The type of the license is unfortunately not depending on me so I’ll try one last time with the CC license and the new improvements. Thank y

Re: [R-pkg-devel] cpp11 and "non-API calls to R"

2024-07-11 Thread Chung-hong Chan
Not from CRAN, also not in a position to opine on cpp11 status, but I wrote about it recently. My solution for readODS back then was to vendor cpp11 and remove the SET_LENGTH call manually, like . But back then CRAN might not know about this. I think it should be easier now. https://www.chainsawri

Re: [R-pkg-devel] Options "reset" when options(opts)

2024-07-11 Thread David Hugh-Jones
This surprised me, even though it shouldn’t have done. (My false internal model of the world was that oo <- options(); … options(oo) would overwrite the entire options list with the old values.) I wonder if it would be worth pointing out explicitly in ?options. Writing: wyclif.substack.com Book: w