badmonkeys.blogg.se

MRAN is a snapshot mirror of CRAN, using this template will allow the package to build even when out-of-date.

Here are three templates of PKGBUILDs for three repositories: MRAN, CRAN and Bioconductor. R has built-in support for building packages. R packages avalable on Bioconductor are available at the website bcname_ or bcname_ where bcname is the name of the package on Bioconductor and bcver the version. Gcc-fortran is needed as depends for some packages but is not always listed in the DESCRIPTION file.Īll R packages available on CRAN are available at the website cranname_ where cranname is the name of the package on CRAN and cranversion the cran version. Some packages require external tools, these are listed under SystemRequirements.

R packages listed in Suggests should be listed as optdepends.

R packages listed in Depends, Imports, or the LinkingTo fields in a package's DESCRIPTION file should be listed under depends. If the package's CRAN webpage has NeedsCompilation: yes it is likely architecture-specific. 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. 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