Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Comparison · Infra & APIs
carrier vs pkgcache
A side-by-side editorial comparison of carrier and pkgcache — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-lib
carrier vs pkgcache: at a glance
What is carrier?
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.
What is pkgcache?
The metadata cache under pak now speaks to authenticated and corporate repositories.
pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.
carrier vs pkgcache: editorial side-by-side
carrier
0.0INFRA · APIS
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
◆ Current state
carrier packages an R function together with the data it needs so it can be shipped to another process or machine. 0.3.0 changed the semantics of functions passed through ...: they are now re-crated inside the main crate environment instead of inheriting from wherever they were defined. That fixes helper functions failing to resolve each other remotely, and stops local environments dragging large objects into the payload.
◆ Where it's heading
Each release tightens the boundary between a crate and its surroundings. 0.2.0 introduced .parent_env defaulting to baseenv() to cut the crate off from the global search path and made unnamed ... arguments an error instead of a silent drop; 0.3.0 finishes the job by controlling the environment chain of the packed closures themselves. The package is trading backwards compatibility for predictable, self-contained payloads — a reasonable bet for something whose failures otherwise surface on a remote worker.
◆ Prediction
The 0.1.0 notes promised an automatic dependency-detection mode to replace explicit packing; nothing since has delivered it, and with the environment semantics now settled that is the obvious next move — though the entries give no date for it.
pkgcache
0.0INFRA · APIS
The metadata cache under pak now speaks to authenticated and corporate repositories.
◆ Current state
pkgcache maintains the package metadata cache that pak and pkgdepends build on, so its releases are about knowing where packages live and what platform they were built for. Version 2.2.4 added support for authenticated repositories through repo_auth(), the first time the cache could reach private registries directly. The releases around it track a moving target: Posit Package Manager behaviour, R Universe binaries, macOS binary availability per R version, Bioconductor version mapping, and most recently comments in DESCRIPTION and PACKAGES files following a change in R-devel.
◆ Where it's heading
The work has shifted from CRAN-shaped assumptions toward the mixed reality of how R packages are actually distributed now — PPM snapshots, R Universe, private and authenticated registries, Bioconductor, and per-platform binaries across several R versions. Resilience is a recurring theme too: 2.2.5 makes an unreachable Bioconductor a non-fatal condition rather than a failure. MRAN's retirement, handled in 2.2.0 by resolving its prefix to PPM, is a reminder of how much of this package's job is absorbing other people's infrastructure changes.
◆ Prediction
Expect continued tracking of R-devel metadata format changes and new binary platforms as R 4.6 lands, since both already appear in 2.2.5. Further work on authenticated repository handling is the plausible follow-on, given how recently that capability arrived.
Alternatives to carrier and pkgcache
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either carrier or pkgcache.
Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
goodpractice
The R package-quality checker returns from CRAN limbo with checks you can select by category.
quarto
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
packrat
R's old dependency manager now runs on a vendored copy of its own successor.
See all carrier alternatives → · See all pkgcache alternatives →
Recent activity from carrier and pkgcache
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agopkgcacheParses comments in DESCRIPTION and PACKAGES files
- 11mo agocarrierCrated helper functions can now see each other ⚡
- 1y agocarriercrate() gains .parent_env and stricter argument handling
- 1y agopkgcacherepo_auth() brings authenticated repositories to the cache ⚡
- 1y agopkgcacheStops using source URLs for archived PPM packages
- 2y agopkgcacheHandles macOS binaries for R 4.5 development builds
- 2y agopkgcacheImproves R to Bioconductor version matching
- 3y agopkgcacheMRAN prefix deprecated in favour of PPM; platform override added
- 3y agocarrierSource references dropped from crated functions
- 4y agocarrierInitial release with explicit-only crate packing
Frequently asked questions
What is the difference between carrier and pkgcache?
Both compete on the same themes — r-lib — within Infra & APIs. carrier and pkgcache are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is carrier better than pkgcache?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. carrier and pkgcache are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to carrier?
Top carrier alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "carrier alternatives" section above for the current picks, or visit /alternatives/carrier for the full list with editorial commentary on each.
What are the best alternatives to pkgcache?
Top pkgcache alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "pkgcache alternatives" section above for the current picks, or visit /alternatives/pkgcache for the full list with editorial commentary on each.