I can't comment on the specific intersection of your plans and CRAN's rules, but
note that you might want to check out the rappdirs package (already on CRAN
and imported by some other packages) as a possible helper for whatever you
decide to do.
https://cran.r-project.org/package=rappdirs
-- Jenn
Hi Sebastian,
Many packages on CRAN have the problem yours exhibits and, as they update, will
also need to address it. In mid-March Kurt Hornik emailed the associated
maintainers to notify them that their package's README.html uses images that do
not ship with the package.
Here's the most impo
rum up responses from the R community.
-- Jenny Bryan
> Begin forwarded message:
>
> From: GitHub Open Source Team
> Subject: Share the Open Source Survey
> Date: April 21, 2017 at 8:24:52 AM PDT
> To: je...@rstudio.com
>
> Hi Jennifer,
>
> Thanks for your interes
Hi Glenn,
It sounds like you should create an environment for your package. If you store
these objects in the global environment, they are exposed to the user and, more
importantly, user could modify or delete them. If you use an environment
specific to your package, you can be sure you are the
The "Generating Rd files" vignette has a paragraph on "Roxygen templates".
vignette("rd", package = "roxygen2")
but I grant you it's not terribly detailed.
In these situations it can be helpful to search GitHub for other packages that
do the thing you want to do.
This search finds >1400 exampl
> exportPattern("^[[:alpha:]]+") means
It is a regular expression that basically says "export all the things", meaning
the functions provided by your package. I regard it as a placeholder to make
things work temporarily, while you get yourself organized for more proactive
management of NAMESPAC
> On Nov 21, 2015, at 7:07 PM, Peter Meissner wrote:
>
> Hey,
>
> I am not sure, that this is the right list for questions that are 'only
> mildly' related to package developement. Your question is more about
> API/webscraping etc. .
>
> Maybe someone can point to a better place to post ques
