On Tue, May 1, 2012 at 1:56 PM, Robert Schweikert <rjschwei@suse.com> wrote:
On 05/01/2012 01:48 PM, Philipp Thomas wrote:
On Tue, 01 May 2012 14:23:11 +0200, "K?ištof Želechovski" <yecril71pl@gmail.com> wrote:
All things R go to %{_libdir}/R, including documentation, localisation and shared data. Why is that so? Is this novel approach a good thing?
I'd say this was done by somebody that didn't have a clue as that is definitely wrong.
Well, that depends, if R works in a similar way to Matlab then your documentation files need to be next to the code modules or they will not be properly found.
Thus, from a distribution point of view we do not want this, but from an application point of view we might have no choice. Only a person that knows R can determine whether documentation can be split out.
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. 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%3Adeadpoint -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org