2012/5/2 Křištof Želechovski <yecril71pl@gmail.com>:
Dnia środa, 2 maja 2012 08:55:35 Darin Perusich pisze:
R modules/libraries are very much like a perl/python/ruby libraries which are installed into their respective "vendor" or "site" library location. Before everyone starts weighing in on why this or that is the "wrong" way to do something, a little light reading on packaging R libraries might be in order. I'd also recommend taking a look at the R packages for Debian, since they provide a large number of these libraries.
PERL libraries sit under /usr/lib, not under /usr/lib64, which seems better.
I don't known about R, neither I am the person to say something about it. But you have a %perl_vendorarch hierarchy under /usr/lib64 on 64bit system which respect %_arch.
PERL documentation does not sit under /usr/lib (except embedded, but that is duplicated as manual pages). OTOH, R documentation is neither duplicated nor linked to %{_defaultdocdir}. That is not a problem when you use R from the command line because R runs its own server; however, the documentation server does not work from within Cantor. Cantor has a button for accessing on-line documentation but that does not help when off line (and being on line should not be essential for running R).
BTW, I had to patch Cantor to start the R server via the R script because otherwise the server would not start at all. I understand that it is the only supported way; however, the question is whether and why R must be so special.
Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-- Nelson Marques // I've stopped trying to understand sandwiches with a third piece of bread in the middle... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org