R allows packages to have colons and hyphens in their version, this is disallowed in PKGBUILDs. Packages should be named r-pkgname, where pkgname is taken from the Package field from the DESCRIPTION file. You could also visit CRAN, Bioconductor link1, and Bioconductor link2 for all the R packages' information. You can get most of this from inside R by running tools::CRAN_package_db(). Most information can be obtained by looking at the package's DESCRIPTION file. This document covers standards and guidelines on writing PKGBUILDs for R packages. #' A detailed description of what the function does.32-bit – CLR – CMake – Cross – DKMS – Eclipse – Electron – Font – Free Pascal – GNOME – Go – Haskell – Java – KDE – Kernel – Lisp – Meson – MinGW – Node.js – Nonfree – OCaml – Perl – PHP – Python – R – Ruby – Rust – Shell – VCS – Web – Wine #' A very brief description of what your function does We want to write specially formatted comments for it, i.e. the #' comments, so that roxygen2 can automatically build the documentation pages. Let’s say you have a script called my_function.R. Each function should be in its own separate file. It’s likely that you already have functions that you want to create a package for. Step 3: Add functions and write documentation I found this guide to be a helpful start if you want to learn more about software licenses. Note: The GPL-3 license seems to be a commonly recommended license for R packages. Suggests: knitr # optional packages that aren't strictly neededĭescription: What the package does, with more detail. Imports: dplyr # packages you need for the package, aka dependencies Version: 0.1.0 # see Jeff Leek's versioning convention Title: What the Package Does # One line only, Title Case, and no period Below is an example (you will have to remove the “# comments” in your actual DESCRIPTION file).
The DESCRIPTION file basically contains some information about the package. You can do this in RStudio or with your favorite text editor.
0 kommentar(er)
