[Rd] Including data in packages
janko.thyson at ku-eichstaett.de
Thu Oct 14 21:27:39 CEST 2010
thanks for the quick reply. So all datasets, regardless if they should be
hidden from the user, should go into /data? If that's the convention, that's
fine with me. But the problem is that there is no data-directory in
R_HOME/library/2-11.1/mypackage after running R CMD build and R CMD INSTALL.
I've experimented with the options --binary and --use-zip-data but without
I think I don't understand the "optional directory" procedure in general
yet: don't I just need to dump stuff in /data, /inst/doc, /exec etc. and
have them "transferred" (sorry, I don't know a better word) to the tar.gz
and eventually to the installed package?
> -----Ursprüngliche Nachricht-----
> Von: Dirk Eddelbuettel [mailto:edd at debian.org]
> Gesendet: Donnerstag, 14. Oktober 2010 21:18
> An: Janko Thyson
> Cc: r-devel at r-project. org
> Betreff: Re: [Rd] Including data in packages
> On 14 October 2010 at 21:06, Janko Thyson wrote:
> | The thing is that I don't understand how the actual 'transfer'
> happens when
> | the package is build and installed. Where do the objects 'live' after
> | installation and how can I access them after firing
> library(mypackage)? For
> | example, there is a 'data' directory for package 'tm'
> | (R_HOME/R-2.11.1/library/tm) but such a directory is missing even if
> I chose
> | option 3) (as stated above) to get my data included. Also, how can I
> | actually execute the lazyload?
> If in doubt, copy existing packages, preferably recommended ones:
> edd at max:~/src/debian/CRAN$ find -type d -name data | sort
> edd at max:~/src/debian/CRAN$
> The vote is clearly in favour of data/ over inst/data.
> Hth, Dirk
> Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com
More information about the R-devel