You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Ian Cook (Jira)" <ji...@apache.org> on 2021/05/27 13:46:00 UTC
[jira] [Comment Edited] (ARROW-12743) [R] Add additional
DESCRIPTION fields for dev dependencies and update docs accordingly
[ https://issues.apache.org/jira/browse/ARROW-12743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352484#comment-17352484 ]
Ian Cook edited comment on ARROW-12743 at 5/27/21, 1:45 PM:
------------------------------------------------------------
Also see the related discussion here: [https://github.com/apache/arrow/pull/10373#issuecomment-849631610]
For some dev dependencies such as roxygen2, a version of the package _does_ exist on CRAN, but we want the newer dev version of it from GitHub. In such cases, wouldn’t it be fine to just use {{Suggests}} and {{Remotes}} like this:
{code}
Suggests:
roxygen2
Remotes:
r-lib/roxygen2
{code}
{{Config/Needs}} seems more appropriate for dependencies that don’t exist on CRAN at all. The [devtools vignette|http://example.com/] says:
{quote}When you submit your package to CRAN, all of its dependencies must also be available on CRAN. For this reason, {{release()}} will warn you if you try to release a package with a {{Remotes}} field.
{quote}
But that is vague on the question of what happens if all dependencies are on CRAN _and_ there’s a Remotes field.
was (Author: icook):
Also see the related discussion here: [https://github.com/apache/arrow/pull/10373#issuecomment-849631610]
For some dev dependencies such as roxygen2, a version of the package _does_ exist on CRAN, but we want the newer dev version of it from GitHub. In such cases, wouldn’t it be fine to just use {{Suggests}} and {{Remotes}}? {{Config/Needs}} seems more appropriate for dependencies that don’t exist on CRAN at all. The [devtools vignette|http://example.com/] says:
{quote}When you submit your package to CRAN, all of its dependencies must also be available on CRAN. For this reason, {{release()}} will warn you if you try to release a package with a {{Remotes}} field.
{quote}
But that is vague on the question of what happens if all dependencies are on CRAN _and_ there’s a Remotes field.
> [R] Add additional DESCRIPTION fields for dev dependencies and update docs accordingly
> --------------------------------------------------------------------------------------
>
> Key: ARROW-12743
> URL: https://issues.apache.org/jira/browse/ARROW-12743
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Nic Crane
> Priority: Major
>
> Recent updates to the remotes package mean that additional fields can be added to a package's DESCRIPTION and remotes functions can take the field as a parameter and install these additional dependencies: https://github.com/r-lib/remotes/blob/master/NEWS.md#new-functions-and-features
> We could update DESCRIPTION to use these fields and update the docs to use this functionality of remotes instead of having separate references to packages to install.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)