On Sat 26 May 2018 at 21:12, Eli Schwartz via aur-general <aur-general@archlinux.org> wrote:
On 05/26/2018 08:37 PM, Ista Zahn via aur-general wrote:
Hi Alex,
Thanks for doing this. However, it seems your script does not correctly specify system dependencies, which IMO is the main benefit of using pacman instead of install.packages. For example, the sf package should depend on gdal, goes, and proj. Do you plan to fix all these dependencies?
Best, Ista
This is why anatolik's quarry repo whitelists the packages it will build, and includes a configuration system for teaching ruby gems how to depend on system dependencies, inject necessary patches, and do other overrides for gems which don't work using just the barebones generated PKGBUILD.
Which is sort of the point here -- it's ridiculous to autogenerate 13K PKGBUILDs, then upload them to the AUR without testing them.
Thanks for the feedback. I was under the (apparently mistaken) impression that CRAN didn't allow packages that required system dependencies other than R and a few compilers. I'll look into if there's a way to get that info. Alex