-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support declaring extra dependencies #459
Comments
I think So for your site you would typically do We can also have |
I was wondering why |
I wonder if |
Closed by #483 |
As discussed on slack, we want to formalize declaring several types of development dependencies in the description file. These are packages that are not needed to pass check, but used for development. E.g:
By declaring these, we can automate rendering docs without having to do custom stuff in the travis file, or making these packages a requirement for running CMD check (as Suggests does).
The proposal is to prefix the fields with
Config/Depends/
such that they do not trigger a NOTE.Fields may contain remotes syntax like
cran::dplyr@0.8.2, r-lib/roxygen@branch
.We generalize the
dependencies
parameter from theremotes::install_...()
functions to support these custom dependencies such as"pkgdown"
.One open question is the dependency relationship between the dependency types :) For example:
This should probably dependencies in
Config/Depends/pkgdown
plus hard dependencies (Depends, Imports, LinkingTo), but not maybe Suggests (which are mostly required to run tests)?The text was updated successfully, but these errors were encountered: