Dear Isaac, В Mon, 22 Apr 2024 17:00:27 +0000 "Petersen, Isaac T" <isaac-t-peter...@uiowa.edu> пишет:
> This my first post--I read the posting guidelines, but my apologies > in advance if I make a mistake. Welcome to R-package-devel! You're doing just fine. > 1) The first note <...> includes the contents of the LICENSE file It's multiple NOTEs in a trench coat. Kasper has addressed the "large version components" and the DOIs interpreted as file URIs, but there's one more. The '<standard license code> + file LICENSE' syntax has two uses: (1) for when the terms of the license is a template, requiring the author of the software to substitute some information (e.g. the year and the copyright holder for MIT) and (2) for when a package puts additional restrictions on the base license. (Hmm. Only case (2) is currently described at <https://cran.r-project.org/doc/manuals/R-exts.html#Licensing>; case (1) is only described inside the license files.) The CRAN team has expressed a preference for the package authors not to put 20000 twisty little copies of standard licenses, all slightly different, inside their packages. Since you're not restricting CC BY 4.0, it's enough to say 'License: CC BY 4.0'. If you'd like a full copy of the license text in your source code repository, that's fine, but you'll need to list the file in .Rbuildignore: https://cran.r-project.org/doc/manuals/R-exts.html#Building-package-tarballs Speaking of the Creative Commons license: the choice of a license for your code is obviously yours, but Creative Commons themselves recommend against using their licenses for software: <https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software>. I can't recommend you a license - that would be politically motivated meddling in foreign affairs - but the lists linked by the CC FAQ and Writing R Extensions section 1.1.2 should provide a good starting point. > Here are the results from win-builder: > https://win-builder.r-project.org/incoming_pretest/petersenlab_0.1.2-9033_20240415_212322/ There is one more NOTE: >> * checking examples ... [437s/438s] NOTE >> Examples with CPU (user + system) or elapsed time > 5s >> user system elapsed >> load_or_install 349.410 37.410 387.233 >> vwReg 35.199 0.379 35.606 The examples are not only for the user to read in the help page; they are also for the user to run example(vwReg) and see your code in action (and for R CMD check to see whether they crash, including regularly on CRAN). For vwReg, try reducing the number of regressions you are running (since your dataset is mtcars, which is already very compact). For load_or_install, we have the additional issue that running example(load_or_install) modifies the contents of the R library and the search path, which belong to the user. The CRAN policy forbids such modifications: <https://cran.r-project.org/web/packages/policies.html> Examples in general should change as little of the global state of the R session and the underlying computer as possible. I suggest wrapping the example in \dontrun{} (since everything about load_or_install() is about altering global state) and creating a test for the function in tests/*.R. The test should set up a new library under tempdir(), run load_or_install(), check the outcomes (that the desired package is attached, etc.) and clean up after itself. There's also the matter of the package not failing without a connection to the Internet, which is another CRAN policy requirement. You might have to bring a very small test package in inst/extdata just for load_or_install() to install and load it, so that R CMD check won't fail when running offline. -- Best regards, Ivan ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
