[opensuse-packaging] All things R
All things R go to %{_libdir}/R, including documentation, localisation and shared data. Why is that so? Is this novel approach a good thing? Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, 01 May 2012 14:23:11 +0200, "K?itof 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. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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
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%3Adeadpoint
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
El 01/05/12 08:23, Křištof Želechovski escribió:
All things R go to %{_libdir}/R, including documentation, localisation and shared data. Why is that so? Is this novel approach a good thing?
Chris
No, It is not novel, it is a very common way called "wrong" :-) Where is that written ? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Dnia wtorek, 1 maja 2012 23:14:39 Cristian Rodríguez pisze:
El 01/05/12 08:23, Křištof Želechovski escribió:
All things R go to %{_libdir}/R, including documentation, localisation and shared data. Why is that so? Is this novel approach a good thing?
No, It is not novel, it is a very common way called "wrong" :-)
Where is that written ?
If you ask how we arrived in this confusing situation, this is what "make install" gives you. Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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. http://cran.r-project.org/doc/manuals/R-admin.html#Add_002don-packages http://fedoraproject.org/wiki/Packaging:R http://cran.r-project.org/bin/linux/debian/README -- Later, Darin On Wed, May 2, 2012 at 2:26 AM, Křištof Želechovski <yecril71pl@gmail.com> wrote:
Dnia wtorek, 1 maja 2012 23:14:39 Cristian Rodríguez pisze:
El 01/05/12 08:23, Křištof Želechovski escribió:
All things R go to %{_libdir}/R, including documentation, localisation and shared data. Why is that so? Is this novel approach a good thing?
No, It is not novel, it is a very common way called "wrong" :-)
Where is that written ?
If you ask how we arrived in this confusing situation, this is what "make install" gives you.
Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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. 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
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
Dnia środa, 2 maja 2012 23:48:50 Nelson Marques pisze:
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.
Here is my @INC: /usr/lib/perl5/site_perl/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.14.2 /usr/lib/perl5/vendor_perl/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.14.2 /usr/lib/perl5/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/5.14.2 /usr/lib/perl5/site_perl/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.14.2 /usr/lib/perl5/site_perl Observe that there is no trace of /usr/lib64. Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
That would be %perl_sitelib and not %perl_vendorarch... vendor arch is quite real I'm afraid. Please see http://fedoraproject.org/wiki/Packaging:Perl. 2012/5/3 Křištof Želechovski <yecril71pl@gmail.com>:
Dnia środa, 2 maja 2012 23:48:50 Nelson Marques pisze:
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.
Here is my @INC:
/usr/lib/perl5/site_perl/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.14.2 /usr/lib/perl5/vendor_perl/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.14.2 /usr/lib/perl5/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/5.14.2 /usr/lib/perl5/site_perl/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.14.2 /usr/lib/perl5/site_perl
Observe that there is no trace of /usr/lib64.
Chris
-- 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
Dnia czwartek, 3 maja 2012 20:09:02 Nelson Marques pisze:
That would be %perl_sitelib and not %perl_vendorarch... vendor arch is quite real I'm afraid. Please see http://fedoraproject.org/wiki/Packaging:Perl.
Those binary things should remain under /usr/lib64 of course, but it is just a tiny core of R. Everything else is misplaced. Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (6)
-
Cristian Rodríguez -
Darin Perusich -
Křištof Želechovski -
Nelson Marques -
Philipp Thomas -
Robert Schweikert