Unofficial Redox OS Repository Builder, builds these in GitHub CI:
- Packages similar to static.redox-os.org/pkg
- Toolchains similar to static.redox-os.org/toolchain
As of June 2025, Redox OS supports custom repository, see how.
- I have forks and I wanted to test it without waiting the official build server
- I don't want to compile heavy packages in my own laptop
I have prebuilt package repos and toolchain.
To use my prebuilt package in existing RedoxOS:
- Download and run latest images
- Run
sudo echo "https://wellosoft.github.io/redox-os-builder" > /etc/pkg.d/40_custom - Run
sudo pkg install ...any pkgs you want
The packages artifacts is in the other repo, and I only update it when I need it. To make your own version, please fork this repository.
I also built toolchain that made for aarch64-unknown-linux-gnu hosts in my personal server so Podman in MacOS can run the toolchain without Rosetta. To use it, adjust relevant constants in mk/config.mk and mk/prefix.mk.
Fork, clone this repo, and run bash setup-full.sh.
Go to Actions tab and enable CI there. Then, go to Run setup-full.sh and click Run Workflow.
Make sure the GitHub action has read and write access (the menu is in Settings > Actions > [scroll down] Read and write permissions).
First, make sure that there are files in gh-pages branch.
Go to settings, pages, Choose deploy from branch and set the branch as gh-pages.
It's a public key for pkg utils verifiying signatures in .pkgar files. By default, it's generated and changed every time you want to rebuild.
To persist it across builds, add PRIVATE_KEY and PUBLIC_KEY to action secrets. The value can be obtained from cookbook/build/id_ed25519.toml and cookbook/build/id_ed25519.pub.toml after doing local build.
Note that GitHub secrets can't have multi line so you need to replace it with commas. With that, the typical format for PRIVATE_KEY value should be:
salt = "XXX", nonce = "YYY", skey = "ZZZ"
Interesting question. The last build took 90 minutes with 25GB storage on /mnt storage. The GitHub CI is generous enough even without subscription. Free GitHub account gives you free 2000 minutes CI and apparently 70GB in /mnt storage. Just read here for GitHub runners.
Generally I think you can cook all recipes if you wish, but it will definitely take longer. Currently I don't cook compilers like LLVM, Cargo and RustPython or even other stuff like games because it's not necessary to me yet.
Of 90 minutes cook recipe from last build, it consist of 8 minutes building tooling and 7 minutes on fetching. It's counting about 66 recipes. The detailed timeline is this:
2025-06-09T00:41:32.5758317Z - start
2025-06-09T00:49:36.7999268Z - prefix done
2025-06-09T00:56:27.9442671Z - fetch.sh done
2025-06-09T02:09:39.2612776Z - repo.sh done
2025-06-09T02:09:47.8987185Z - done
Incremental builds requires PRIVATE_KEY and PUBLIC_KEY set since initial full build. You can't set it after initial full build otherwise the public keys will be invalid for old pkgar files.
After pushing your own changes in the repo, you can run Run setup-partial.sh GitHub Action. There will be an input about list of recipes you want to update — for example if you put "nano vim" then the CI will run make prefix f.nano r.nano f.vim r.vim and updates the repo files and repo.toml accordingly.
I think there's no tool for that yet, but I made online viewer for it.