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

Improve revdep_check documentation #635

Closed
hadley opened this Issue Nov 4, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@hadley
Member

hadley commented Nov 4, 2014

Describing what happens with the output.

@hadley hadley closed this in 66f951a Nov 5, 2014

@hofnerb

This comment has been minimized.

hofnerb commented Dec 12, 2014

I am not completly sure what happens in revdep_check(pkg = "somepackage") .

Are you using the currently installed version of somepackage or is the package also downloaded from CRAN? And/or can I specify a path to the package instead of the package name (as in other devtools functions such as check) and run the reverse check on this package? I think the documentation should clarify these issues.

EDIT: I now do understand that revdep_check() needs to access CRAN in order to determine the reverse dependencies. However, I think one could add this to the manual (and the question which version of somepackage is used in this check stays open).

hadley added a commit that referenced this issue Dec 12, 2014

@hadley

This comment has been minimized.

Member

hadley commented Dec 12, 2014

Just pushed some doc improvements. Please let me know if that doesn't answer your question.

@hofnerb

This comment has been minimized.

hofnerb commented Dec 12, 2014

Great, thank you very much!

@lock

This comment has been minimized.

lock bot commented Sep 18, 2018

This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/

@lock lock bot locked and limited conversation to collaborators Sep 18, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.