[R-pkg-devel] CRAN-compatible location for output of example code?

2019-07-04 Thread Michael Gruenstaeudl
Assume an R package that generates a figure ('output.pdf') as the result 
of executing the example code specified in one of the manual files (i.e. 
an .Rd file). The example code specifies the figure to be saved to the 
root directory of the package (i.e., where files DESCRIPTION and 
NAMESPACE are located).


\examples{
...
outFile <- paste(getwd(), "output.pdf", sep="")
...
}

Upon submitting the package to CRAN, I receive the NOTE that the 
following note:


Flavor: r-devel-linux-x86_64-debian-gcc
Check: for non-standard things in the check directory, Result: NOTE
  Found the following files/directories:
'output.pdf'

To which folder should I have the example code save the output file in 
order for the code to be compatible with the CRAN submission guidelines?


__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


[R-pkg-devel] VignetteBuilder field

2019-07-03 Thread Michael Gruenstaeudl
Assume an R package `myPackage` that contains the folder `vignettes`, in 
which the TEX-file `PACViR_Vignette.tex` and two image files 
(`image1.pdf` and `image2.pdf`) are located. The TEX-file compiles 
nicely without the need to use Sweave or knitr.


Upon testing the package for submission to CRAN via `R CMD check PACViR 
--as-cran`, I receive the following NOTES, which appear to prevent CRAN 
from accepting my package:



Flavor: r-devel-windows-ix86+x86_64
Check: files in 'vignettes', Result: NOTE
  Package has no Sweave vignette sources and no VignetteBuilder field.

Flavor: r-devel-linux-x86_64-debian-gcc
Check: files in ‘vignettes’, Result: NOTE
  Package has no Sweave vignette sources and no VignetteBuilder field.


What is needed to address this issue? Do I need to specify a 
`VignetteBuilder` somewhere?


__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel


[R-pkg-devel] Installing conda dependecy onAttach

2019-06-14 Thread Michael Gruenstaeudl
Assume an R package (`myRpackage`) that has a conda package 
(`condaDependecy`) as a system requirement. The file `DESCRIPTION` of 
the R package would read like:


Package: myRpackage
...
SystemRequirements: condaDependecy (>= 0.1)
...

How can I ensure the automatic installation of this condaDependecy (i.e. 
`conda install condaDependency`) upon installing the R package itself 
(i.e. `install.packages("myRpackage")`), assuming that myRpackage is 
listed on CRAN?


I would prefer a method less "clunky" as

.onAttach = function(libname = find.package("myRpackage"), pkgname 
= "myRpackage") {

system("conda install -y condaDependency")
}

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel