On 02/03/2010 09:12 PM, Paul Johnson wrote:
> One of the really handy R packaging ideas they have
> is to customize R environment so that there are several directories in
> the package path.
>
> It adjusts the etc/Renviron file so that it has:
>
> R_LIBS_USER=${R_LIBS_USER-'~/R/i486-pc-linux-gnu-library/2.10'}
> R_LIBS_SITE=${R_LIBS_SITE-'/usr/local/lib/R/site-library:/usr/lib/R/site-library:/usr/lib/R/library'}
>
> That would be pretty easy to add into the R packaging for RPM systems.
>
> The benefit is as follows.
>
> If an unprivileged user tries to install an R package, there's no
> error, but rather it installs the rpm under $HOME/R/i386.
Well, I don't think a standard setup will permit an unprivileged user to
install rpm packages, but this should work when building things from
CRAN, I suppose.
My only concerns are:
1) Users shouldn't be assuming that /usr/local/lib/R exists. Fedora
packages can't create that directory, and we don't really want the first
user to hit that directory to create it with their own ownership privs.
2) Right now, we have two locations for R packages from Fedora:
%{_libdir}/R/library/* and %{_datadir}/R/library/* (arch vs noarch). I'm
not sure it is worth making another set of separate directories.
Or to sum it up, I think the R_LIBS_USER setting makes some sense, but
I'm not sure the additional complexity of R_LIBS_SITE adds any value.
Also, I'm not sure why there is so much hierarchy in the proposed
setting for R_LIBS_USER. The R version, perhaps is understandable, but
the target architecture?
> "Over there" in r-sig-deb, I learned that Dirk Eddelbuettel and
> Charles Blundell developed a thing called "cran2deb".
>
> http://www.mail-archive.com/debian-science@xxxxxxxxxxxxxxxx/msg03306.html
>
> That has debian packages of almost every R package you can get on CRAN.
I'm not personally a fan of autogenerated packages. If people are
interested in a CRAN package, we can get it added to Fedora and properly
maintained. The number of times that RScaLAPACK has broken has convinced
me of the value of having someone responsible for keeping these bits
alive. :)
With that said, various folks have made some good tools for making quick
and easy R module RPM packages, and those are an excellent first step
for getting those packages into Fedora.
~spot
_______________________________________________
r-devel mailing list
r-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/r-devel
