A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/r-lib/revdepcheck below:

r-lib/revdepcheck: R package reverse dependency checking

pak::pkg_install("r-lib/revdepcheck")

Check package in working directory, creating "revdep/" directory if it doesn't already exist:

revdep_check(num_workers = 4)

If the run fails to complete, run again and it will pick up where it left off:

revdep_check(num_workers = 4)

During execution, run these in a separate R process to view status completed checks:

revdep_summary()                 # table of results by package 
revdep_details(".", "<package>") # full details for the specified package

Generate human-friendly summary documents in revdep/:

revdep_report()
## Writing *partial* report
## Writing summary to 'revdep/README.md'
## Writing problems to 'revdep/problems.md'
## Writing failures to 'revdep/failures.md'

Manage a "todo" list of packages to examine:

revdep_add(pkg = ".", <packages>)  # add <packages> to the list
revdep_rm(pkg = ".", <packages>).  # remove <packages> from list

revdep_add_broken()  # add all broken packages
revdep_add_new()     # add newly available packages
revdep_todo()        # list packages in the todo list

Clear out all previous results

We recommend running revdep_check() in a separate process (e.g. new terminal under RStudio). That way, while it runs in a background tab, you can easily use your revdep_details(revdep = "pkg") to see what's gone wrong with "pkg".

MIT © Gábor Csárdi, R Consortium, RStudio Inc


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4