I have at various times tried the built-in (tools package) solution;
fairly complex hand-rolled stuff I did myself; and revdepcheck. I found
that revdepcheck handled installation of needed dependencies, including
caching packages where necessary, more easily. It felt like the 'tools'
machinery
Not sure why nobody dicusses the R internal check functionality, also
for reverse dependencies, from the tools package?
That is what CRAN uses for the reverse dependency checks.
Best,
Uwe Ligges
On 11.04.2018 23:14, J C Nash wrote:
Another workaround is to use
tlogl <- readLines(attr(cpkg.
Indeed these are useful for one of my present tasks. Thanks. JN
On 2018-04-11 03:10 PM, Georgi Boshnakov wrote:
>
> Hi,
>
> Not really an answer but I only recently discovered devtools::revdep(),
> which automates checking reverse dependencies.
>
> Georgi Boshnakov
>
>
>
>
> ___
Another workaround is to use
tlogl <- readLines(attr(cpkg.chk, "path"))
Possibly this may suggest a way to improve functionality.
JN
On 2018-04-11 03:24 PM, Henrik Bengtsson wrote:
> R CMD check, which is used internally runs checks in standalone
> background R processes. Output from these is
I got several responses to my query. Henrik's does suggest "why", but I
am rather unhappy that R has this weakness. (See below for a sort of
workaround for Linux users.)
In particular, note that the check_built() function DOES return an object,
but it does NOT print().
In fact, putting alldep <-
R CMD check, which is used internally runs checks in standalone
background R processes. Output from these is not capturable/sinkable
by the master R process. The gist of what's happening is:
> sink("output.log")
> system("echo hello") ## not sinked/captured
hello
> sink()
> readLines("output.lo
Hi,
Not really an answer but I only recently discovered devtools::revdep(), which
automates checking reverse dependencies.
Georgi Boshnakov
From: R-package-devel [r-package-devel-boun...@r-project.org] on behalf of J C
Nash [profjcn...@gmail.com]
