| 19 Nov 2025 |
 K900 | Same thing | 18:13:30 |
 Emma [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 etc | 18:13:50 |
| K900 | It would be significantly easier if you could just have { buildPlatform, hostPlatform } as arguments to your outputs function | 18:14:01 |
| K900 | Or something like that | 18:14:20 |
| K900 | You should have that option | 18:14:36 |
| K900 | But I don't think it should be the default | 18:14:41 |
| K900 | I actually really appreciate the choice Cargo makes here | 18:14:51 |
| K900 | The final artifact is always locked | 18:14:57 |
| K900 | But the intermediate dependencies are cross-resolved | 18:15:04 |
 ghpzin | It has plenty of other weird gotchas. | 18:15:32 |
 Katalin 🔪 | 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 [it/its] | i dont mind it being the default - i tend to use that detail a lot myself | 18:15:56 |
| Katalin 🔪 | 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 |
| Katalin 🔪 | and only when building standalone, should it supply its own locked dependencies | 18:17:18 |
| Katalin 🔪 | 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 | 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 | Except bug fixes | 18:21:16 |
 Zoe Z | On a clean checkout of 2.94.0 😦
57/144 lix:installcheck / functional-repl FAIL 1.38s exit status 1
| 21:22:39 |
 Rutile (Commentator2.0) feel free to ping | Yeah, those are quite flakey | 22:14:40 |
| Rutile (Commentator2.0) feel free to ping | Give me a couple of <del>weeks</del> months and maybe ill get those migrated to f2 as well | 22:15:42 |
| Zoe Z | It's failing because it's getting a different error message before it's hitting a filesystem boundary when searching for the flake. Is there a cleaner way to fix it than just checking for both messages? | 22:57:28 |
 Jules Lamur | Hi, is the Lix infra repo https://git.lix.systems/lix-project/web-services still available somewhere (or is it private)? It's mentionned on the wiki here https://wiki.lix.systems/books/lix-infrastructure-guide/page/machine-and-service-overview but it's a 404 as a guest. | 23:02:02 |
|  ellie joined the room. | 23:09:53 |
| K900 | The Lix infra repo is private, what are you looking for? | 23:17:37 |
| Jules Lamur | I was just curious :) I expected it to be public since it was mentionned there but it makes sense that it's private. | 23:19:16 |
| K900 | Stuff is slowly moving over to afnix infra which is public | 23:21:22 |
| K900 | https://git.afnix.fr/afnix/infra | 23:21:22 |
| ellie | oh wow lol does lix really not have that many build servers | 23:50:14 |
 just1602 | In reply to @rv32ima:envs.net
oh wow lol does lix really not have that many build servers If you have extras you can donate them to afnix! 😅 | 23:56:12 |
| Jules Lamur | In reply to @k900:0upti.me
Stuff is slowly moving over to afnix infra which is public Ok now that's interresting :) That's the first time I hear about afnix. Digging its public matrix channels does not immediatly clarify (to me at least) what the goal of the association is or what the relationship exactly is between afnix and lix. Do you have any resources about it? Is lix independant from afnix? | 23:56:10 |
