From: Ricardo Wurmus <rekado@elephly.net>
To: 47664@debbugs.gnu.org
Subject: bug#47664: CRAN importer does not parse “Remotes” field.
Date: Thu, 08 Apr 2021 22:42:20 +0200 [thread overview]
Message-ID: <87a6q8y0cz.fsf@elephly.net> (raw)
The CRAN importer can be used to import packages from CRAN and
Bioconductor, but also from arbitrary git and hg repositories.
Especially for code published as a git/hg repository the “Remotes” field
of the DESCRIPTION file can be important.
The bedtorch[1] package, for example, has a DESCRIPTION file like this:
--8<---------------cut here---------------start------------->8---
Package: bedtorch
Type: Package
Title: R package for fast BED-file manipulation
Version: 0.1.8
Authors@R:
person(given = "Haizi",
family = "Zheng",
role = c("aut", "cre"),
email = "haizi.zh@gmail.com")
Description: The goal of bedtorch is to provide a fast BED file manipulation tool suite native in R.
License: MIT + file LICENSE
Encoding: UTF-8
LazyData: true
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.1.1
Depends:
R (>= 4.0)
Imports:
stringr,
dplyr,
purrr,
tidyr,
data.table,
R.utils,
assertthat,
Rcpp,
Rhtslib12,
RCurl
Suggests:
testthat (>= 3.0.0),
devtools (>= 2.3.0),
zoo
Config/testthat/edition: 3
URL: https://github.com/haizi-zh/bedtorch
BugRePORTS: https://github.com/haizi-zh/bedtorch/issues
BiocType: Software
Remotes:
haizi-zh/Rhtslib12
LinkingTo:
Rcpp,
Rhtslib12
SystemRequirements: GNU make
--8<---------------cut here---------------end--------------->8---
The “Remotes” field specifies the origin for the Rhtslib fork. The
importer should probably try to import the packages from the “Remotes”
field first.
--
Ricardo
reply other threads:[~2021-04-08 20:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6q8y0cz.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=47664@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.