!9IQChSjwSHXPPWTa:lix.systems

Lix

1105 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-rooms295 Servers

Load older messages


SenderMessageTime
13 Oct 2025
@k900:0upti.meK900This is a special case for paths relative and fully contained in flake root10:02:48
@k900:0upti.meK900 I still have no idea why 10:02:55
@mangoiv.:matrix.orgMangoIVoh, i do not wish to partake in that discussion, I just want to explain to myself why I cannot use this nix code with lix that I can use with upstream nix. 10:02:56
@raitobezarius:matrix.orgraitobezariusit's helpful for us to decide what to do10:03:16
@raitobezarius:matrix.orgraitobezariusit's not a debate :)10:03:18
@mangoiv.:matrix.orgMangoIVprobably usability issues? you don't have to update the lock file every time something in the repo changes 10:03:23
@mangoiv.:matrix.orgMangoIVthat is a really good usability feature, fwiw10:03:40
@k900:0upti.meK900The short answer is we didn't backport https://github.com/NixOS/nix/pull/1008910:03:43
@raitobezarius:matrix.orgraitobezariusit makes sense to me to say that relative paths to a locked node are locked10:03:43
@k900:0upti.meK900I don't see a use case where a subpath is actually meaningfully useful as its own flake input unless you're doing weird subflake stuff or submodules10:04:36
@k900:0upti.meK900And you shouldn't do those things10:04:46
@k900:0upti.meK900 And I don't even know if this works with submodules 10:04:56
@k900:0upti.meK900I'm pretty sure this is just some lazy trees nonsense that's three steps removed from the actual rationale10:05:14
@aloisw:julia0815.dealoisw To avoid https://git.lix.systems/lix-project/lix/issues/586 I guess. 10:05:33
@mangoiv.:matrix.orgMangoIVour specific use case is a tutorial. there are two sub directories that each are a separate tutorial and the top level flake import the other flakes to allow checking that they still work 10:05:59
@raitobezarius:matrix.orgraitobezariusthe change above mentioned do change evaluation semantics of the outputs of flakes though10:07:00
@raitobezarius:matrix.orgraitobezariusthat massively sucks10:07:15
@aloisw:julia0815.dealoisw It was extremely broken before though. 10:07:36
@raitobezarius:matrix.orgraitobezariusyou mean subdirs as flake inputs or dependencies of the outputs fields in other values of the flake?10:08:12
@aloisw:julia0815.dealoisw Subdirectories as flake inputs. 10:08:57
@raitobezarius:matrix.orgraitobezariusyeah my remark is not a major blocker10:09:55
@raitobezarius:matrix.orgraitobezariusbut that change is not a trivial thing to port seems like10:10:01
@raitobezarius:matrix.orgraitobezariushttps://git.lix.systems/lix-project/lix/issues/101210:13:19
@raitobezarius:matrix.orgraitobezarius thanks aloisw for helping me to clarify the core feature 10:13:34
@mangoiv.:matrix.orgMangoIV So the answer is
„This is a good change, semantics wise, but poses some technical difficulties and is probably hard to port“?
10:13:38
@raitobezarius:matrix.orgraitobezariusyeah, ideally we should avoid the shortcomings of cppnix's change10:13:56
@mangoiv.:matrix.orgMangoIV I think this is a good answer. For now a workaround is just using the cppnix evaluator in a shell. Maybe you can add that to the issue.
Thank you!
10:15:20
@raitobezarius:matrix.orgraitobezariusadded the workaround10:16:01
@tarynnya:matrix.orgMoonstoneHearts changed their display name from tarynnya to MoonstoneHearts.10:17:36
@sofiedotcafe:matrix.orgSofie 🏳️‍⚧️ (she/her)photo.jpg
Download photo.jpg
10:37:14

Show newer messages


Back to Room ListRoom Version: 10