[aur-general] Packaging all CRAN packages for R

Alex Branham alex.branham at gmail.com
Thu May 31 15:03:39 UTC 2018

On Wed 30 May 2018 at 20:53, Eli Schwartz <eschwartz at archlinux.org> wrote:

> So, I looked into this a bit.
> https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#The-DESCRIPTION-file
> Looks like the rule is, if NeedsCompilation = yes, then the package
> contains C or Fortran code which must be compiled into an ELF library foo.so
> In this case, the PKGBUILD should specify arch=('x86_64') and
> additionally any other architectures you feel comfortable supporting in
> the AUR package.
> In the case where NeedsCompilation = no, then the package contains only
> R code which is byte-compiled, but can run on any architecture and
> should therefore specify arch=('any')

Thanks for looking into this. I had assumed that NeedsCompilation dealt
with byte compiling the R code (only in the most recent R version did
byte compilation get enabled by default).

I've updated the R packages I maintain to take advantage of this.


More information about the aur-general mailing list