Just made a package for the nightly binaries for the arch user repository.
https://aur.archlinux.org/packages/roc-nightly-bin
Problem is that the released tarballs, and more importantly their names, are changed frequently.
It would be easier to package if there was a roc_nightly-linux_x86_64.tar.gz
duplicating whichever named tarball is the newest.
Can something be done on that front?
Maybe we can name it -latest
. Should be totally doable with an update to our nightly workflow.
That would also let us add a one line install script to the Roc readme/website if that's something people want
I'd like to set up a long term reliable solution, so I suggest we set up roc-lang.org/download where we make all nightlies available and with fixed URLs for the latest nightly. I'll try to get that done next week.
These should be long term links that get updated five days a week:
https://github.com/roc-lang/roc/releases/download/nightly/roc_nightly-linux_x86_64-latest.tar.gz
https://github.com/roc-lang/roc/releases/download/nightly/roc_nightly-macos_apple_silicon-latest.tar.gz
https://github.com/roc-lang/roc/releases/download/nightly/roc_nightly-macos_x86_64-latest.tar.gz
I'm still uploading with the old filenames as well because I expect that the github action created by @Hannes relies on the old format.
I'm currently updating CI scripts and will get started on roc-lang.org/download next.
I'm not yet sure how I'm going to handle making old nightlies available for download, netlify has an option for file serving but it may not be the best fit. Feel free to weigh in if you have experience with ddos proof (cold) file storage.
I'm not yet sure how I'm going to handle making old nightlies available for download
:thinking: is it a given that we need to?
I wonder if torrents or IPFS may be useful if you want to keep historical versions?
I'm not yet sure how I'm going to handle making old nightlies available for download
:thinking: is it a given that we need to?
My thinking was it is very useful to be able to download the exact nightly that a prebuilt platform was built with. If you have a version mismatch other workarounds could be quite time-consuming.
Anton said:
I'm still uploading with the old filenames as well because I expect that the github action created by Hannes relies on the old format.
I've just checked my code and turns out it doesn't rely on the old format. It finds all the assets containing the OS and architecture name and then picks the most recently released one, so it works fine with the new names!
Nice and robust :)
Last updated: Jul 06 2025 at 12:14 UTC