Windmill
Windmill is dismantling the paywall between itself and the data stack
Comparison · Infra & APIs
pkgbuild vs vdiffr
A side-by-side editorial comparison of pkgbuild and vdiffr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-libmaintenance
pkgbuild vs vdiffr: at a glance
What is pkgbuild?
A package whose release calendar is written by whoever ships the next Rtools.
pkgbuild is the layer devtools and pak use to run R CMD build and R CMD INSTALL, and most of what it does is know where the compiler is. Six of its last eight releases are about Rtools: supporting Rtools43, 44 and 45, finding installations that did not come from an installer, reading the Windows registry correctly again, and handling aarch64 Windows when the expected environment variable is unset. The feature surface is a handful of Config/build/* DESCRIPTION options for packages with unusual build needs.
What is vdiffr?
vdiffr finished its job in 2021 and has been tracking compilers ever since.
vdiffr generates deterministic SVG snapshots so plot changes show up as test failures. Its recent history is almost entirely toolchain: UCRT Windows compatibility twice, a revert to C++11 to work around a GCC issue, and renaming the internal SVG device so it stops colliding with svglite. The only functional additions in view are snapshot variants in 1.0.8 and a testthat fix so snapshots are no longer auto-deleted when a test errors or skips. The last release was October 2024.
pkgbuild vs vdiffr: editorial side-by-side
pkgbuild
0.0INFRA · APIS
A package whose release calendar is written by whoever ships the next Rtools.
◆ Current state
pkgbuild is the layer devtools and pak use to run R CMD build and R CMD INSTALL, and most of what it does is know where the compiler is. Six of its last eight releases are about Rtools: supporting Rtools43, 44 and 45, finding installations that did not come from an installer, reading the Windows registry correctly again, and handling aarch64 Windows when the expected environment variable is unset. The feature surface is a handful of Config/build/* DESCRIPTION options for packages with unusual build needs.
◆ Where it's heading
This is maintenance defined entirely by other people's release schedules — R minor versions, Rtools versions, and the DESCRIPTION options downstream package authors ask for. The one structural change worth noting is that on R 4.3 and later the package stopped special-casing Windows and now tests for build tools by compiling a small package, the same way it always has on Unix. That is the direction: fewer platform branches, more probing.
◆ Prediction
Expect the next release to add support for whichever Rtools ships alongside the next R minor version, and expect the Windows registry lookups to keep shrinking as the compile-probe approach proves out.
vdiffr
0.0INFRA · APIS
vdiffr finished its job in 2021 and has been tracking compilers ever since.
◆ Current state
vdiffr generates deterministic SVG snapshots so plot changes show up as test failures. Its recent history is almost entirely toolchain: UCRT Windows compatibility twice, a revert to C++11 to work around a GCC issue, and renaming the internal SVG device so it stops colliding with svglite. The only functional additions in view are snapshot variants in 1.0.8 and a testthat fix so snapshots are no longer auto-deleted when a test errors or skips. The last release was October 2024.
◆ Where it's heading
The package reached its intended shape at 1.0.0, when snapshot management moved to testthat and vdiffr shed most of its own R and JavaScript code to become a reproducible SVG engine and nothing more. There is not much left to add to that, and the release stream since reads accordingly: it moves when a compiler, an R version, or testthat moves. For a testing dependency this is a healthy end state, though it does mean the package inherits whatever the graphics engine does to snapshot stability.
◆ Prediction
The entries do not support predicting a feature release. The likely next change is a compatibility fix prompted by a compiler or a testthat change, as every release since 1.0.2 has been.
Alternatives to pkgbuild and vdiffr
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 pkgbuild or vdiffr.
Resend
Resend is wiring itself into every agent runtime it can reach, one standard at a time
rsconnect
The deployment client is being rebuilt around credentials it never has to store.
DNSControl
DNSControl v5 is feature complete and counting down to an August ship date
highr
highr is finished software: one-line releases every year or two
git2r
git2r stopped vendoring libgit2 and now expects it on the system
See all pkgbuild alternatives → · See all vdiffr alternatives →
Recent activity from pkgbuild and vdiffr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agopkgbuildnever-clean build option; aarch64 Windows Rtools detection
- 1y agopkgbuildWindows build-tool detection now probes by compiling
- 1y agovdiffrSnapshot variants supported
- 1y agopkgbuildFix Rtools 4.3 and 4.4 discovery on Windows
- 2y agopkgbuildSupport R 4.4.x and Rtools44
- 2y agopkgbuildDrops crayon, rprojroot and prettyunits dependencies
- 2y agovdiffrRevert to C++11 for a GCC workaround
- 2y agovdiffrRename internal SVG device to avoid svglite collision
- 3y agopkgbuildbootstrap.R now runs under pkgbuild_process and pak
- 4y agovdiffrUCRT Windows compatibility under Rtools42
- 4y agovdiffrUCRT Windows compatibility
- 5y agovdiffrSnapshots survive errored and skipped tests
Frequently asked questions
What is the difference between pkgbuild and vdiffr?
Both compete on the same themes — r-lib, maintenance — within Infra & APIs. pkgbuild and vdiffr 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 pkgbuild better than vdiffr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. pkgbuild and vdiffr 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 pkgbuild?
Top pkgbuild alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "pkgbuild alternatives" section above for the current picks, or visit /alternatives/pkgbuild for the full list with editorial commentary on each.
What are the best alternatives to vdiffr?
Top vdiffr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "vdiffr alternatives" section above for the current picks, or visit /alternatives/vdiffr for the full list with editorial commentary on each.