r-package

i'm trying to build a R package, but it seems that there are some problems with the package dependencies. If I run the code in R, I need the packages "rgdal" and "rgeos", so for creatng the package out of it, I: Added the line "import(rgdal, rgeos)" to the NAMESPACE file Added the line "Depends: rgeos, rgdal" to the DESCRIPTION file When I run R CMD check (after build) I got an error which says: * checking package dependencies ... ERROR Benötigte, aber nicht verfügbare Pakete: 'rgeos' 'rgdal' See the information on DESCRIPTION files in the chapter 'Creating R packages' of the 'Writing R

Consider this R package with two functions, one exported and the other internal hello.R #' @export hello <- function() { internalFunctions:::hello_internal() } hello_internal.R hello_internal <- function(x){ print("hello world") } NAMESPACE # Generated by roxygen2 (4.1.1): do not edit by hand export(hello) When this is checked ( devtools::check() ) it returns the NOTE There are ::: calls to the package's namespace in its code. A package almost never needs to use ::: for its own objects: ‘hello_internal’ Question Given the NOTE says almost never , under what circumstances will a package need to

I have created an R package that I would like to submit to CRAN. It contains code that needs to be compiled (plain C) and this code depends on the libxml2 library. My current solution is to let Linux and Mac users install the libxml2-dev package, which lets them compile and install the R source package. For Windows I have created a special binary R-package that contains the needed binary dependencies. When reading the CRAN guidelines I see that only source packages may be uploaded and that they may not contain any binary files. My questions are then: Is it ok for Mac/Linux to have the user

I am working on a package which includes C code from third-party library (SUNDIALS). The package compiles and works (i.e., is able to solve a test ODE) with the following Makevars file performing static linking CXX=clang++ PKG_CPPFLAGS = -I../inst/include PKG_LDFLAGS = /usr/local/lib PKG_LIBS= $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) $(PKG_LDFLAGS)/libsundials_cvode.a $(PKG_LDFLAGS)/libsundials_nvecserial.a However, a slightly modified version (based on the example in R-Exts, i.e. - PKG_LIBS = -L$(XML_DIR)/lib -lxml2 ) of Makevars (below) fails CXX=clang++ PKG_CPPFLAGS = -I../inst/include PKG

Can someone point me towards a working example where packrat is used with AppVeyor to build an R package? Searching through Google and GitHub, I can't find any packrat-enable package that uses AppVeyor. Does the appveyor.yml file need to change? Are there some settings I need to add through the AppVeyor website? I have a very minimal package ( testthat is the only dependency) that broke AppVeyor builds. Here is the code frozen for that commit . Here is the AppVeyor log . (If this SO question sounds familiar, I'm about to ask a similar question for Travis-CI .) Ben Yes, the solution here is

When I run R CMD check --as-cran on my package, the one note I still get is: checking CRAN incoming feasibility ... NOTE Maintainer:[my name] <my email> I can't seem to find a good explanation of this note, although I haven't read anything that tells my I should be concerned about it. As anyone else run into this? Is there anything I can do that will clear the note? According to CRAN Maintainer Uwe Ligges, This is just a note that reminds CRAN maintainers to check that the submission comes actually from his maintainer and not anybody else. Thus, it is safe to ignore such a message. These

I've written a few functions for a package that use relative paths like: "./data/foobar.rds" Here's an example function: foo <- function(x) { x <- readRDS("./data/bar.rds") return(x) } Now, if I were to be working in the development path of the package, this works as I expect. But when I load the package, this path uses the current working directory rather than the relative path of the package. How does one set it up such that the path for functions within a package maintain their within the package relative paths? As Andrie notes, you can use system.file , which "finds the full file names of