Designing Nextest's Install Scripts Cargo-nextest author Rain (the project's maintainer) released install scripts for the Rust test runner four and a half years after the first cargo-nextest version, adding install.sh for Unix-like platforms including WSL, Cygwin and Git Bash and install.ps1 for Windows. The scripts are invoked via `curl -LsSf https://get.nexte.st/install.sh | sh` and `irm https://get.nexte.st/install.ps1 | iex`, and the maintainer said the work took over a month of intermittent effort and was built with coding agents to meet a high quality bar. The scripts replace the previous tarball-extraction approach, which required a five-line PowerShell command on Windows and could not automatically select a statically linked musl build on Linux when the system glibc was too old or absent. Designing nextest’s install scripts ../../posts/nextest-install-scripts/ Four and a half years after I released the first version of cargo-nextest https://nexte.st/ , it now has install scripts This has been a long time coming, and I’m really happy to finally have support for them. On Unix-like platforms, including WSL, Cygwin https://www.cygwin.com/ , and Git Bash for Windows https://gitforwindows.org/ MSYS https://www.msys2.org/ , you can now run install.sh https://get.nexte.st/install.sh : curl -LsSf https://get.nexte.st/install.sh | sh On Windows, you can also use PowerShell with install.ps1 https://get.nexte.st/install.ps1 : irm https://get.nexte.st/install.ps1 | iex I wanted to write a bit about why it took so long to publish them, how they work, and how I used coding agents to meet a high quality bar. Background background We’ve published release binaries for the nextest project since its very earliest versions https://nexte.st/changelog/ 0.9.4 in 2022. When initially designing support for release binaries, I spent some time looking at the options for how to deliver them to users. The usual approach is an install script that you curl | sh or irm | iex , but I determined that: - Writing install scripts is quite difficult. You have to maintain separate Unix and Windows scripts, each with its own hazards, and test in a myriad of different situations. My general philosophy while writing infrastructure is to build things in a way that I don’t have to think about them again, and I felt that any install script would have a long tail of issues I’d have to chase down. I didn’t think I had the skills required to write one that lived up to my own standards. - Many users quite understandably do not like curl | sh , and it would be a mistake for that to be the only way to install release binaries