On Tue, 1 May 2012 14:25:24 -0400, Darin Perusich <darin@darins.net> wrote:
As you've said this depends, but typically yes, everything needs to be installed within the R library directory, %{_libdir}/R/library. With R things like documentation and such are really only accessed from an R session or the R help system, and for R to find it it must be next to the code as you say. Having said that, it might be possible to move some things, like certain documentation, outside %{_libdir}/R/library, but you run the risk of breaking the help system.
Then the code needs to be changed in a way that you can install it in a standards conforming way and that would be /usr/bin for binaries, /usr/lib(64) for libraries, /usr/share/<app_name> for non-binary data and so on.
For those that care to look, I started building a number of R modules/libraries a while ago and the spec's are in this project of mine. I also packaged the R2spec tool which is much like cpanspec for perl to simplify package creation.
R-modules project: https://build.opensuse.org/project/show?project=home%3Adeadpoint%3AR-modules
R2spec: http://widehat.opensuse.org/repositories/home:/deadpoint/ https://build.opensuse.org/package/show?package=R2spec&project=home%3Adeadpo...
When time permits, which at least currently is rare, I'll take a look. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org