{
  "id": 20242368,
  "title": "Designing nextest's install scripts",
  "url": "https://urgent.news/2026/11/16/designing-nextests-install-scripts",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-16T00:14:56.000Z",
  "source": {
    "name": "Lobsters",
    "slug": "lobsters",
    "url": "https://sunshowers.io/posts/nextest-install-scripts/"
  },
  "original_language": "en",
  "account": "After releasing the initial version of cargo-nextest four and a half years ago, it has now been equipped with install scripts. This development has been eagerly anticipated, and the author is pleased to finally provide support for them on Unix-like platforms, including WSL, Cygwin, and Git Bash for Windows (MSYS). On Windows, users can also utilize PowerShell with install.ps1. The lengthy process of creating these scripts is attributed to various factors, such as the need for release binaries, the choice of delivery methods, and the desire to maintain a high quality bar.\n\nInitially, the author explored options for delivering release binaries, considering an install script that could be executed via curl | sh or irm | iex. However, it was determined that using tarballs (and a zip file for Windows) and asking users to extract the files themselves would be a more effective approach. For instance, on Linux, one would run a command that extracts the tarball, while Windows users would execute a PowerShell command.\n\nOver time, the author realized that the Windows instructions were quite complex, spanning five lines and not easily displayed on the home page. Additionally, on Linux, there was no way to automatically select a statically-linked musl build if the system version of glibc was too old or not present. The author believed that install scripts would be necessary in the long term, leading to the creation of a pair of scripts that have been tested to work in various situations, even under multiple failure modes.\n\nAn install manifest was also developed, which contains text files with archive URLs and checksums for each version. This manifest is designed to be easily parseable using standard word-splitting utilities like read in Unix shells and -split in PowerShell. The shell script is compatible with any Bourne shell, while the PowerShell script works on both version 5.1 and PowerShell 7.\n\nThe installation process involves several steps and relies on various validation techniques, including automated test harnesses, manual code review, and comprehensive testing. Although LLMs were employed to assist in the development process, the author emphasized the importance of manual review and careful validation to ensure the highest level of quality and rigor.",
  "summary": null,
  "key_points": [
    "Install scripts added to cargo-nextest after four years",
    "Scripts supported on Unix-like platforms, Windows via PowerShell",
    "Install manifest with archive URLs and checksums for versions"
  ],
  "editors_take": "Automating the setup process across diverse Unix-like and Windows environments lowers the barrier to entry for users while ensuring consistent, high-quality installations through rigorous validation and standardized manifests.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}