Today I saw an error from CRAN that I did not see in Win-builder or on
my system with Ubuntu Linux. This is from the CRAN Debian test system:
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... OK
* checking re-building of vignette outputs ... [6
Can you advise me about this warning in package check:
Package has a VignetteBuilder field but no prebuilt vignette index.
In my vignette folder, I do have an "index.html" file, the index in
the installed package is fine. But I still get this package build
warning:
I asked same question on stac
Note that your attachment was lost, so we don't know what your package code
looks like. It's helpful to host your package sources somewhere publicly
accessible (e.g. GitHub) to make it easier for others to access sources
quickly from a web browser.
My best guess is that your 'init.c' is missing th
> On 12 Aug 2018, at 00:18, peter dalgaard wrote:
>
> Have you tried asking CRAN for help? I mean, if you don't fix an obvious
> error, with a well-known cause, like the log thing, they'll get fed up and
> throw you off. However, fixing and then discovering an issue elsewhere is
> different, e
On 13.08.2018 16:51, Duncan Murdoch wrote:
On 13/08/2018 9:08 AM, Eggleston, Barry wrote:
Hello,
I am working through my first submission and making good progress with
the CRAN review system, but now I need to understand the best practice
for dealing with helper functions. I am building a
On 13/08/2018 9:08 AM, Eggleston, Barry wrote:
Hello,
I am working through my first submission and making good progress with the CRAN
review system, but now I need to understand the best practice for dealing with
helper functions. I am building a package that only exports 12 functions for
di
There are several other things to do. You might find the toy package
fooRegister I use for teaching helpful.
https://github.com/cjgeyer/foo/tree/master/package/fooRegister
--
Charles Geyer
Professor, School of Statistics
Resident Fellow, Minnesota Center for Philosophy of Science
University of M
Thanks everybody. And just to clarify, it is no why that CRAN knew the
functions in question were helper functions. From their perspective, I just
had a lot of .Rd files with ‘#none’ under @examples. Since these files under
question are not directly accessible to the user, I will try the
#' @
Do you have to export them? If not, I think you can just leave out the
@export from the roxygen2 comments.
Here is what I did for my package:
https://github.com/boxuancui/DataExplorer/blob/master/R/helper.r
Best,
Boxuan (Bo)
On Mon, Aug 13, 2018 at 2:08 PM Eggleston, Barry wrote:
>
> > Hello,
You can add
#' @noRd
to those functions and roxygen2 will not generate .Rd files for those
entries.
On Mon, Aug 13, 2018 at 2:08 PM Eggleston, Barry wrote:
> Hello,
>
> I am working through my first submission and making good progress with the
> CRAN review system, but now I need to understand
Hi Barry,
could you specify wh osked you to provide examples? R CHECK doesn't give me
any warnings. If it was asked by the people of CRAN itself, you can explain
that these are internal functions and the help pages are only there for
reference to advanced users. But I'm not sure if they'll accept
Hello,
I am working through my first submission and making good progress with the CRAN
review system, but now I need to understand the best practice for dealing with
helper functions. I am building a package that only exports 12 functions for
direct user access, but it has many helper function
12 matches
Mail list logo
