!9IQChSjwSHXPPWTa:lix.systems

Lix

1119 Members
Lix user channel. Feel free to discuss on-topic issues here and give each other help. For matrix.to links to the rest of the Lix channels, see: https://wiki.lix.systems/books/lix-organisation/page/matrix-rooms300 Servers

Load older messages


SenderMessageTime
27 Dec 2025
@daslixou:matrix.orgdaslixouwinnow, I see16:23:01
@piegames:flausch.socialpiegamesSo to set expectations, the timeline for amy of this is "hopefully still in 2026 but no guarantees"16:23:17
@piegames:flausch.socialpiegames* So to set expectations, the timeline for any of this is "hopefully still in 2026 but no guarantees"16:23:31
@daslixou:matrix.orgdaslixouRedacted or Malformed Event16:23:32
@daslixou:matrix.orgdaslixoutime to make a lix account iguess16:26:27
@daslixou:matrix.orgdaslixou 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 16:36:08
@madmccrow:matrix.orgmadmccrow It's more like : I don't like the way to have latest and stable nixpkgs side by side when developing for machines with radically different missions (ie. Gaming desktop, vs backup NAS) .
If you add the fact that the flake layout might require you to have some inputs twice ( like for example if you wanna use Lanzaboote with both stable and latest).
A lockfile by machine would be better by a mile, but I don't know how to do it without splitting my work in multiple repos.
Because I've read that the lix community wasn't satisfied with flakes in it's current state, I would have thought some alternative was being used.
16:51:34
@acidbong:envs.netAcid Bong then have two Nixpkgs inputs and define hosts from them, there's no problem with that 16:53:28
@quadradical:federated.nexusQuadRadical (Ping) but i suppose it would cause you to potentially download an extra unused copy of nixpkgs 16:54:18
@k900:0upti.meK900 lanzaboote should be an overlay no? 16:56:51
@piegames:flausch.socialpiegames
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:matrix.orgdaslixouno like, from what other parser is it?17:05:57
@daslixou:matrix.orgdaslixouthe 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 elsewhere17:08:51
@madmccrow:matrix.orgmadmccrow Yeah. It is, but for flakes you have to have it in input and use the follows notation. 17:35:49
@k900:0upti.meK900You don't necessarily17:36:56
@k900:0upti.meK900The nixpkgs flake input should not be used if you're using the NixOS module17:37:05
@madmccrow:matrix.orgmadmccrowSee, 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:0upti.meK900Overlays are generally the Right Way17:50:01
@k900:0upti.meK900Specifically for this very reason17:50:05
@piegames:flausch.socialpiegames
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:flausch.socialpiegames(The insanity is partially courtesy of horrors)18:05:06
@madmccrow:matrix.orgmadmccrow

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:0upti.meK900Secrets are mostly solved with agenix/sops-nix tbh18:12:16
@k900:0upti.meK900Like yes there are some other issues but that covers most of the common use cases18:12:30
@daslixou:matrix.orgdaslixou 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:flausch.socialpiegamesWell I've been on it for only a couple of days so it really isn't much19:22:23
@jyrama:garm.jrd.fijyramaBtw, speaking of lanzaboote, has anyone noticed any uncompression problems with lix 2.93.3 and lanzaboote?20:43:34
@raitobezarius:matrix.orgraitobezariuswhat does that look like?20:43:56
@raitobezarius:matrix.orgraitobezarius"failed to read compressed data" ?20:44:01
@jyrama:garm.jrd.fijyramaMine downloads some blob to the nix store and then fails to extract the xz archive20:44:04

Show newer messages


Back to Room ListRoom Version: 10