Skip to content
Git

Contributing & Help

Contributions are welcome!

In fact, this project can only be sustained in the longterm if the community actively contributes, both in terms of regular infrastructure maintenance and individual package curation.

The most helpful contributions at the moment are ones which investigate in detail why specific packages failed to build a binary. This usually comes down to a missing system dependency (which is either not declared in the package's DESCRIPTION file or "exotic" and requires installation from source) or a C code compile issue.

The most effective way to report such issues is to create an issue in the upstream repository of the affected R package.

Please do not open issues or write emails related to package loading issues at runtime or general repository configuration issues. Depending on the package, certain system libraries are required at runtime as binaries do not necessarily bundle the required system libraries.

rpkgs.com does not (or only in rare exceptions) apply custom patches to the underlying build infrastructure to fix single package builds.
Expections are only made when these might have a a positive effect on multiple packages or if the inclusion of an exotic system library allows a specific package to build successfully (and in turn all of its downstream dependencies.)

👉️ If you are convinced that there is an issue with package from the CRAN repository caused by a misconfiguration in the rpkgs.com build environment, please open an issue in the build-cran-binaries repository.

👉️ If you are having an R-related issue with building binaries yourself, i.e. caused by a bug or a missing feature in {bincraft}, please open an issue in the {bincraft} repository.

👉️ If you have found an issue with the rpkgs-build-env images, please open an issue in the build-env-images repository.