| 20 Nov 2025 |
 Zelda 🏳️⚧️ [she/her] | gulp 😨 | 20:31:26 |
|  willow changed their profile picture. | 23:17:55 |
| willow changed their profile picture. | 23:18:02 |
| willow changed their profile picture. | 23:19:22 |
| 21 Nov 2025 |
| willow removed their profile picture. | 00:04:09 |
| willow set a profile picture. | 00:04:39 |
 llakala | my issue was marked as a release blocker - i feel so special! | 02:10:00 |
| llakala | ty mr bezarius of snix rpc fame | 02:10:30 |
 raitobezarius | :p | 14:46:43 |
 Sofie 🏳️⚧️ (she/her) | once we eventually have a governance committee for Lix, do you think these would be reasonable goals software‑wise for lix
the things I’m most curious about are:
- a standardized flake replacement (or some kind of agreed‑upon standard for flakes)
- a more “native” tool for deploying to multiple machines, including local ones, the current ones feel clunky. nixopsv4 is interesting at least
- secure build environments (e.g. something that provides a safe way to handle auth/tokens in builds)
- and maybe, someday, even bit‑exact builds
| 17:31:20 |
 522 it/its ⛯ΘΔ | bit-exact builds as in "it's impossible to even make a non-reproducible build in nix"?
| 17:33:26 |
 K900 | 1) out of scope
2) out of scope
3) already being considered
4) bit-exct builds of? | 17:34:46 |
 Charles | i feel like Reproducible Builds has to be considered out of scope, since all a nix implementation can really do there is ensure reproducible build environments | 17:44:29 |
| Charles | it's up to both the existence of a reproducible build environment and the software being built to support Reproducible Builds | 17:45:11 |
| Sofie 🏳️⚧️ (she/her) | ah, yea | 17:45:11 |
| Sofie 🏳️⚧️ (she/her) | I mean, there are some issues but they are fixed already
I also once found an binary that every time when u download it, has a different hash | 17:46:02 |
| Charles | i.e. reproducible build environments are necessary but not sufficient to achieve Reproducible Builds | 17:46:08 |
| Sofie 🏳️⚧️ (she/her) | is this more like, clangs job now? | 17:46:33 |
| Sofie 🏳️⚧️ (she/her) | like | 17:46:41 |
| Sofie 🏳️⚧️ (she/her) | we have the environment | 17:46:45 |
| Charles | no, it's the job of every piece of software involved in producing the artifacts | 17:46:54 |
| Sofie 🏳️⚧️ (she/her) | ah | 17:47:03 |
| Charles | source code, compilers, build scripts, etc; things of that nature | 17:47:03 |
| Sofie 🏳️⚧️ (she/her) | what would be the most finniky part currently? | 17:47:25 |
| Charles | all a nix implementation can do is ensure that the build environment is bit-exact reproducible, not the output artifacts from any given build | 17:47:34 |
| Charles | bitching at every upstream to write deterministic code for generating outputs of any form | 17:48:00 |
| Sofie 🏳️⚧️ (she/her) | ooo, 3? | 17:48:26 |
| Charles | getting the current date? not reproducible. iterating a hashmap? not reproducible. etc. | 17:48:39 |
 piegames | (btw we do have governance since this summer) | 17:49:45 |
| 522 it/its ⛯ΘΔ | running builds in an environment that always does stuff like iterate files in alphabetical order would at least work around reproducibility issues | 17:51:00 |
