Section 1.1.6 of the Writing R Extensions describes the use of the inst/extdata
directory for any type or organization of data that you want to keep in the
package. None of the directories should be assumed to be writeable though... if
you want to write data then do it in the temporary directory or let the user
decide where to put it.
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<jdnewmil at dcn.davis.ca.us> Basics: ##.#. ##.#. Live
Go...
Live: OO#.. Dead: OO#.. Playing
Research Engineer (Solar/Batteries O.O#. #.O#. with
/Software/Embedded Controllers) .OO#. .OO#. rocks...1k
---------------------------------------------------------------------------
Sent from my phone. Please excuse my brevity.
On January 24, 2015 6:44:39 AM PST, Glenn Schultz <glennmschultz at
me.com> wrote:>Hello All,
>
>I am nearing the end of the Package BondLab. ?This package is for the
>analysis of structured securities (MBS, REMICs, and Mortgage
>derivatives). ?I would like to submit to CRAN but the folder structure
>is not standard. ?Indeed, I plan to reorganize the folder structure
>outside the package folder. ?This will require the following:
>
>Current data and cusip examples will be moved to Data folder.
>Next, I would like the package to create the outside data folder
>structure and move the cusip and structuring data
>to?the?appropriate?folders.
>CRAN rules seem to allow this is the session is interactive? ?Is this
>correct? ?If so what is the preferred way of accomplishing this?
>I have made the package public on git hub for
>today?https://github.com/glennmschultz/BondLab.git
>If CRAN does not allow the files to be written at all I am still
>interested in accomplishing the above
>Best Regards,
>Glenn
>
>______________________________________________
>R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see
>https://stat.ethz.ch/mailman/listinfo/r-help
>PLEASE do read the posting guide
>http://www.R-project.org/posting-guide.html
>and provide commented, minimal, self-contained, reproducible code.