CRAN importer does not parse “Remotes” field.

OpenSubmitted by Ricardo Wurmus.
One participant
  • Ricardo Wurmus
Ricardo Wurmus wrote on 8 Apr 22:42 +0200
(address .
The CRAN importer can be used to import packages from CRAN andBioconductor, but also from arbitrary git and hg repositories.Especially for code published as a git/hg repository the “Remotes” fieldof the DESCRIPTION file can be important.
The bedtorch[1] package, for example, has a DESCRIPTION file like this:
Toggle snippet (44 lines)Package: bedtorchType: PackageTitle: R package for fast BED-file manipulationVersion: 0.1.8Authors@R: person(given = "Haizi", family = "Zheng", role = c("aut", "cre"), email = "")Description: The goal of bedtorch is to provide a fast BED file manipulation tool suite native in R.License: MIT + file LICENSEEncoding: UTF-8LazyData: trueRoxygen: list(markdown = TRUE)RoxygenNote: 7.1.1Depends: R (>= 4.0)Imports: stringr, dplyr, purrr, tidyr, data.table, R.utils, assertthat, Rcpp, Rhtslib12, RCurlSuggests: testthat (>= 3.0.0), devtools (>= 2.3.0), zooConfig/testthat/edition: 3URL: SoftwareRemotes: haizi-zh/Rhtslib12LinkingTo: Rcpp, Rhtslib12SystemRequirements: GNU make
The “Remotes” field specifies the origin for the Rhtslib fork. Theimporter should probably try to import the packages from the “Remotes”field first.
-- Ricardo