Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-06-14 Thread Duncan Murdoch
On 13/06/2020 9:00 p.m., Gábor Csárdi wrote: On Sat, Jun 13, 2020 at 8:10 PM Duncan Murdoch wrote: On 13/06/2020 1:17 p.m., Zhian Kamvar wrote: [...] Is this a new policy? Zhian, it seems that some of the problematic links are created by roxygen2. You can fix these using this PR: https://g

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-06-14 Thread Gábor Csárdi
On Sun, Jun 14, 2020 at 10:44 AM Duncan Murdoch wrote: [...] > > I think the argument was that static builds of the help pages would have > trouble resolving the links. With the current system, you can build a > help page that links to a page in package foo even if package foo is not > installed

Re: [R-pkg-devel] check cross-references error: Non-file package-anchored link(s)

2020-06-14 Thread Duncan Murdoch
I agree with almost everything you wrote, except one thing: this isn't newly enforced, it has been enforced since the help system began. What I think is new is that there are now tests for it. Previously those links just wouldn't work. Duncan Murdoch On 14/06/2020 6:26 a.m., Gábor Csárdi w

[R-pkg-devel] Problem with test data folder. R package develpoment

2020-06-14 Thread Subhadip Datta
I attached my test data in inst/data but why this warning is showing. "Found the following non-empty subdirectories of 'inst' also used by R: inst/data It is recommended not to interfere with package subdirectories used by R." This is not a problem from my side. It used the data from that

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

2020-06-14 Thread Joshua N Pritikin
I'm trying to include vignettes that take much too long for CRAN check. At the beginning of the Rmarkdown vignette, I use is_CRAN <- !identical(Sys.getenv("NOT_CRAN"), "true") if (is_CRAN) q() And then I use export NOT_CRAN=true when I build locally. But CRAN check still complains, On

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

2020-06-14 Thread Joshua N Pritikin
I'm trying to include vignettes that take much too long for CRAN check. At the beginning of the Rmarkdown vignette, I use is_CRAN <- !identical(Sys.getenv("NOT_CRAN"), "true") if (is_CRAN) q() And then I use export NOT_CRAN=true when I build locally. But CRAN check still complains, On

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

2020-06-14 Thread Joshua N Pritikin
I'm trying to include vignettes that take much too long for CRAN check. At the beginning of the Rmarkdown vignette, I use is_CRAN <- !identical(Sys.getenv("NOT_CRAN"), "true") if (is_CRAN) q() And then I use export NOT_CRAN=true when I build locally. But CRAN check still complains, On

Re: [R-pkg-devel] Problem with test data folder. R package develpoment

2020-06-14 Thread Jeff Newmiller
Use a different name than "data" such as "rawdata" within "inst" to put files that your code refers to using the system.name() function. The directory name "data" is used for a specific purpose as described in the Writing R Extensions manual [1], and if you want to put files in that directory fo

Re: [R-pkg-devel] Problem with test data folder. R package develpoment

2020-06-14 Thread Duncan Murdoch
On 14/06/2020 4:55 a.m., Subhadip Datta wrote: I attached my test data in inst/data but why this warning is showing. "Found the following non-empty subdirectories of 'inst' also used by R: inst/data It is recommended not to interfere with package subdirectories used by R." This is no

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

2020-06-14 Thread Iñaki Ucar
On Sun, 14 Jun 2020 at 14:32, Joshua N Pritikin wrote: > > > I'm trying to include vignettes that take much too long for CRAN check. > > At the beginning of the Rmarkdown vignette, I use > > is_CRAN <- !identical(Sys.getenv("NOT_CRAN"), "true") > if (is_CRAN) q() > > And then I use > > expor

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

2020-06-14 Thread Duncan Murdoch
On 13/06/2020 1:29 p.m., Joshua N Pritikin wrote: I'm trying to include vignettes that take much too long for CRAN check. At the beginning of the Rmarkdown vignette, I use is_CRAN <- !identical(Sys.getenv("NOT_CRAN"), "true") if (is_CRAN) q() And then I use export NOT_CRAN=true whe

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

2020-06-14 Thread Joshua N Pritikin
Ah, thank you! Sorry for the duplicate posts. On Sun, Jun 14, 2020 at 09:17:32AM -0400, Duncan Murdoch wrote: > On 13/06/2020 1:29 p.m., Joshua N Pritikin wrote: > > > > I'm trying to include vignettes that take much too long for CRAN check. > > > > At the beginning of the Rmarkdown vignette, I

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

2020-06-14 Thread Joshua N Pritikin
On Sun, Jun 14, 2020 at 09:17:32AM -0400, Duncan Murdoch wrote: > Since you're using Rmarkdown, you can use a variable for the eval > chunk option, e.g. put this in your setup chunk: > > knitr::opts_chunk$set(eval = !is_CRAN) This works except for in-text `r 1+1` code fragments. Is there an opti

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

2020-06-14 Thread Duncan Murdoch
On 14/06/2020 10:59 a.m., Joshua N Pritikin wrote: On Sun, Jun 14, 2020 at 09:17:32AM -0400, Duncan Murdoch wrote: Since you're using Rmarkdown, you can use a variable for the eval chunk option, e.g. put this in your setup chunk: knitr::opts_chunk$set(eval = !is_CRAN) This works except for in

Re: [R-pkg-devel] [CRAN-pretest-archived] CRAN submission gwsem 2.0.3

2020-06-14 Thread Joshua N Pritikin
Ah, brilliant. Thanks. On Sun, Jun 14, 2020 at 11:28:17AM -0400, Duncan Murdoch wrote: > On 14/06/2020 10:59 a.m., Joshua N Pritikin wrote: > > On Sun, Jun 14, 2020 at 09:17:32AM -0400, Duncan Murdoch wrote: > > > knitr::opts_chunk$set(eval = !is_CRAN) > > > > This works except for in-text `r 1+1