| 27 Dec 2025 |
 K900 | lanzaboote should be an overlay no? | 16:56:51 |
 piegames | In reply to @daslixou:matrix.org
I have to ask, from where are the whole stateful, bytecode, parserstate and thunk things from? I want to make sense of how they'd be used That's locally defined in the same file, ignore the bytecode scaffolding that's for later | 17:05:35 |
 daslixou | no like, from what other parser is it? | 17:05:57 |
| daslixou | the bytecode thing looks similar to rustpython, but then it's pretty different afterall and I haven't seen such direct mapping from parser to bytecode elsewhere | 17:08:51 |
 madmccrow | Yeah. It is, but for flakes you have to have it in input and use the follows notation. | 17:35:49 |
| K900 | You don't necessarily | 17:36:56 |
| K900 | The nixpkgs flake input should not be used if you're using the NixOS module | 17:37:05 |
| madmccrow | See, to me, it looks like the famous xkcd comic about too many standards. I feel like every nix project uses a slightly different approach, making my OCPD twitch looking at imperfect code. | 17:45:27 |
| K900 | Overlays are generally the Right Way | 17:50:01 |
| K900 | Specifically for this very reason | 17:50:05 |
| piegames | In reply to @daslixou:matrix.org
the bytecode thing looks similar to rustpython, but then it's pretty different afterall and I haven't seen such direct mapping from parser to bytecode elsewhere It's from nowhere because that's my own code. Probably nobody sane would attempt single-pass compailation directly in the parser | 18:02:44 |
| piegames | (The insanity is partially courtesy of horrors) | 18:05:06 |
| madmccrow | Exactly my thoughts. I kinda regret the old /nix/etc way of having a config there, and downloading and building only what's necessary.
I feel like Flakes are very interesting for developing projects and reusable libraries, but they feel way too limiting for managing machines ( secrets, impurities, etc., are still an unsolved issue in my - probably uneducated - opinion)
| 18:10:45 |
| K900 | Secrets are mostly solved with agenix/sops-nix tbh | 18:12:16 |
| K900 | Like yes there are some other issues but that covers most of the common use cases | 18:12:30 |
| daslixou | Oh 🫣 I'm terribly sorry, I just assumed it as it was the first commit, didn't mean to offend you | 19:10:43 |
| piegames | Well I've been on it for only a couple of days so it really isn't much | 19:22:23 |
 jyrama | Btw, speaking of lanzaboote, has anyone noticed any uncompression problems with lix 2.93.3 and lanzaboote? | 20:43:34 |
 raitobezarius | what does that look like? | 20:43:56 |
| raitobezarius | "failed to read compressed data" ? | 20:44:01 |
| jyrama | Mine downloads some blob to the nix store and then fails to extract the xz archive | 20:44:04 |
| raitobezarius | if so, this is not a lanzaboote interaction problem | 20:44:07 |
| jyrama | Sound familiar yes… | 20:44:15 |
| raitobezarius | curl --version ? | 20:44:20 |
| jyrama | On my way home, will check that on arrival | 20:44:53 |
| raitobezarius | np | 20:45:08 |
| raitobezarius | i feel like there was a sensible reason which was like we should always check for cgroups, especially to discover above cases | 20:45:56 |
| raitobezarius | i wonder what to think about nix on droid which doesn't seem to have a valid cgroupv2 filesystem mounted | 20:46:33 |
| raitobezarius | it feels like an unsupported configuration, why it doesn't have a cgroupv2 fs? | 20:46:48 |
| raitobezarius | that being said, we should probably be more graceful, for sure | 20:47:05 |
