Skip to content

docs: link to revdepcheck fn #2105

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

Closed
wants to merge 1 commit into from
Closed

docs: link to revdepcheck fn #2105

wants to merge 1 commit into from

Conversation

salim-b
Copy link
Contributor

@salim-b salim-b commented Feb 15, 2025

plus minor tweaks

plus minor tweaks
#' artefacts
#' * Prompts user to run the checks with `revdepcheck::revdep_check()`
#' artefacts.
#' * Prompts the user to run the checks with [revdepcheck::revdep_check()].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't link to a topic in a package that's not on CRAN, which revdepcheck is not.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why can't you link to it? Is there a CRAN rule forbidding this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically you should have a formal dependency on a package to link to its help topics:

https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#Cross_002dreferences-1

Packages referred to by these ‘other forms’ should be declared in the DESCRIPTION file, in the ‘Depends’, ‘Imports’, ‘Suggests’ or ‘Enhances’ fields.

In the past, you can sort of get away with a link to something you don't depend on, sometimes. But I would not go so far for a package that is not even on CRAN.

Also CRAN is now making static HTML reference manuals, which has triggered a big wave of requests to re-release packages cleaning up various documentation loose ends. So if anything, this is all going to get even stricter.

@jennybc jennybc closed this Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants