[R-pkg-devel] Saving binary files in a package

[Thierry Onkelinx]

You have no guarantee that the user has write access to those folders. So
you might want to rethink your strategy.

​
ir. Thierry Onkelinx
Instituut voor natuur- en bosonderzoek / Research Institute for Nature and
Forest
team Biometrie & Kwaliteitszorg / team Biometrics & Quality Assurance
Kliniekstraat 25
1070 Anderlecht
Belgium

To call in the statistician after the experiment is done may be no more
than asking him to perform a post-mortem examination: he may be able to say
what the experiment died of. ~ Sir Ronald Aylmer Fisher
The plural of anecdote is not data. ~ Roger Brinner
The combination of some data and an aching desire for an answer does not
ensure that a reasonable answer can be extracted from a given body of data.
~ John Tukey
Op 4 jul. 2015 05:00 schreef "Glenn Schultz" <glennmschultz at me.com>:

> Hi All,
>
> I am researching the criteria for submitting packages on the R website and
> using Hadley's packages book as a general guide.  The CRAN policy is that a
> package cannot write files.  My question is as follows:
>
> Does this apply when the package is installed only?  I ask because my
> package does not write any files on install.  However, I have functions
> that allow the user to create cusip level information to create a MBS
> security (dated date, first payment date, etc.).  The function then saves
> the file as a binary to the appropiate data folder in the package file
> directories.  I use the same strategy to save mortgage prepayment model
> tuning parameters.
>
> If the result of the function, after a package is installed, is to save a
> data file in the package's subdirectories does this violate CRAN policy
> against writing files?  I read the policy but I am not 100% sure in this
> case.
>
> -Glenn
> ______________________________________________
> R-package-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>

	[[alternative HTML version deleted]]