!9IQChSjwSHXPPWTa:lix.systems

Lix

1103 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-rooms294 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
19 Nov 2025
@emma:rory.gayEmma [it/its] // flake-utils.lib.eachSystem flake-utils.lib.allSystems ( is the only part where i use flake-utils, and that's only for packages outputs 18:12:49
@k900:0upti.meK900So you are in fact using an entire abstraction to express things that are bad18:13:06
@emma:rory.gayEmma [it/its]im merging it into the rest of the structure lol18:13:23
@k900:0upti.meK900Same thing18:13:30
@emma:rory.gayEmma [it/its]i suppose yeah - i meant more the other side of the issue: being able to import a flake and reasonably beign able to expect it to build as it uses it's own definition of nixpkgs etc18:13:50
@k900:0upti.meK900 It would be significantly easier if you could just have { buildPlatform, hostPlatform } as arguments to your outputs function 18:14:01
@k900:0upti.meK900Or something like that18:14:20
@k900:0upti.meK900 You should have that option 18:14:36
@k900:0upti.meK900But I don't think it should be the default18:14:41
@k900:0upti.meK900I actually really appreciate the choice Cargo makes here18:14:51
@k900:0upti.meK900The final artifact is always locked18:14:57
@k900:0upti.meK900But the intermediate dependencies are cross-resolved18:15:04
@ghpzin:envs.netghpzinIt has plenty of other weird gotchas.18:15:32
@saiko:knifepoint.netKatalin 🔪 yeah. something not building should be the exception, it shouldn't be the expectation, that you then have to always work around 18:15:54
@emma:rory.gayEmma [it/its]i dont mind it being the default - i tend to use that detail a lot myself18:15:56
@saiko:knifepoint.netKatalin 🔪 I want to just say "this repo needs nixpkgs (and whatever other dependencies), supply it yourself if you import this repo somewhere" 18:17:09
@saiko:knifepoint.netKatalin 🔪 and only when building standalone, should it supply its own locked dependencies 18:17:18
@saiko:knifepoint.netKatalin 🔪 essentially I want something like what meson does for wrap-files, where only the wrap files in the top-level project are considered 18:18:19
@raitobezarius:matrix.orgraitobezarius
In reply to @emma:rory.gay
also re the announcement, does that note about flakes in vNext mean the UX/commands will be changing, or will it be invisible to users?
No change
18:21:06
@raitobezarius:matrix.orgraitobezariusExcept bug fixes18:21:16

Show newer messages


Back to Room ListRoom Version: 10