[RkWard-devel] Gentoo ebuild

[Thomas Friedrichsmeier]

Hi Juan,

On Wednesday 10 May 2006 09:28, Juan Manuel Peralta wrote:
> Hi.  I recently found out about rkward (version 0.3.5) and started using
> it. Since I use Gentoo linux, and coudn't find an 'ebuild' for it, I made
> one for it (see the attachment). Today I saw the 0.3.6 release, and found
> that you have an ebuild for it. I inspected it, and saw that you have to
> work around the 'sandboxing' to get the R library compiled and installed. I
> used a different approach in my 0.3.5 ebuild.

the ebuild was contributed by Brian Peterson (braverock at users dot 
sourceforge dot net). See also 
http://sourceforge.net/tracker/index.php?func=detail&aid=1483151&group_id=50231&atid=459009 
and 
http://sourceforge.net/tracker/index.php?func=detail&aid=1482468&group_id=50231&atid=459007 . 
As far as I know, none of the developers has ready access to a gentoo system. 
So for coordination and discussing packaging details you might want to 
contact Brian directly.
Of course still I'm interested in fixing the source distribution of rkward to 
make it easy and clean to package (see below).

> Basically I created a patch for the make file that deals with the R library
> compilation to make R compile a binary package. Then, instead of having R
> installing the package, I unpackage the binary under the image directory
> inside the sandbox environment. This efectively allows installation and
> clean up of rkward under gentoo without sandbox violations and work
> arounds. Oh, and the need for a patch could also be removed if the build
> process of rkward uses the same sort of indirect instalation of the R
> library (compile with R, then unpack where it should go).
> I believe this is a much cleaner approach for an ebuild, and I thought that
> you might be interested in it. In any case, I just wanted to make a tiny
> contribution to a quite useful software.

If I understand the sandbox violation correctly, it comes from the call to R 
CMD INSTALL, which did not honor the DESTDIR setting to make install. 
Therefore the package always got installed to the main R library tree, 
instead of the corresponding directory in the sandbox (could you confirm, the 
sandbox violation comes from the call to R CMD INSTALL, and only that?).
In my local source tree I have now added a configure option --with-r-libdir to 
specify the R library tree to install to. In the Makefile.am in rpackages, I 
now have

install:
	-${R_HOMEDIR}/bin/R CMD INSTALL -l $(DESTDIR)/$(R_LIBDIR) rkward

(added the -l option). I think with this (to be released in the next version) 
no more patch should be needed. Unfortunately, I can not easily produce a 
diff ATM, as sourceforge CVS is down (again). Once CVS becomes available 
again, I'll ask you to test whether this works as expected (I hope I'll 
remember to do so). I could also send you the relevant files in private mail, 
if you like (~150K).

Thanks a lot for your comments, and please let us know, if there are any 
further issues.

Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20060510/f9f2674b/attachment.sig>