Terminal-first R package manager focused on speed and mirror selection
Experience command-line R package management that installs single or multiple packages, picks CRAN mirrors by fuzzy country match, and fetches from git hosts. Alberson Miranda built rpkg as a Rust-based utility for developers and data scientists who prefer shell workflows on Windows and Linux. It offers advanced mirror resolution, GitHub/GitLab/Bitbucket support, and bulk updates, making scripted environment setup and CI/CD automation easier for people who deploy R packages from several sources.
What rpkg does for R package installation
rpkg runs installations from the terminal, replacing interactive R sessions by invoking Rscript from PATH and accepting single or multiple package names in one command. It supports CRAN, custom repositories like R-Universe, and git-based sources including GitHub, GitLab, Bitbucket, and Codeberg. When multiple repository or mirror matches appear, the tool offers an interactive numbered selection to resolve ambiguity.
How it affects system and performance during operations
The tool is written in Rust, which reduces runtime overhead compared with R-based installer scripts and keeps resource use low during package fetch and build steps. Because rpkg shells out to Rscript for the actual installation, CPU and memory behaviour follow R's build process; the Rust layer mainly handles network, mirror resolution, and orchestration with minimal additional load.
Safety, automation, and where you must intervene
rpkg requires Rscript to be present in the system PATH, so environments without R configured need manual setup before automation. It falls back to personal library paths when system libraries are not writable, avoiding permission failures. Interactive selection for ambiguous mirrors or repositories can pause automated runs unless the command sequence explicitly resolves choices, which matters for CI/CD scripting.
Who can use it without deep technical setup
The command-line interface suits users comfortable with shells and CI pipelines: scripting package installs and running rpkg --update for bulk updates fits a developer or data scientist workflow. Windows users can install via WinGet and Linux via Cargo or a PPA, so adopting it usually requires basic platform tooling and PATH configuration rather than changes to R itself.
Good fit for terminal-oriented R maintainers, with a small automation caveat
rpkg is aimed at terminal-focused R developers and data scientists who need fast, scriptable package installs from CRAN and git hosts. It reduces manual steps in environment setup and handles mirror choice intelligently. Expect to maintain a configured Rscript PATH and to handle interactive mirror prompts when you require fully unattended CI runs; these are practical trade-offs for a lightweight CLI workflow.
