| 29 Nov 2025 |
 Grimmauld (any/all) | i wish we had humorous people calling channels that | 17:06:08 |
 K900 | And you should only run stable branches if you know exactly why you're doing that | 17:06:25 |
| Grimmauld (any/all) | i'd argue it depends on whether you want to be confronted with all the breaks one at a time or all at once | 17:06:37 |
| Grimmauld (any/all) | and obviously if you contribute, then you contribute the things you yourself want to use so you probably are on unstable (or even master) to get stuff faster | 17:07:28 |
| K900 | I strongly believe that people who say they want to be confronted with all the breaks at once actually mean they want to be confronted with all the breaks never | 17:07:37 |
| K900 | And that's only valid if you can dispose of the system after it runs out of support time | 17:08:04 |
 hexa | stable for me means I can automate deployments without checking in on things every other week | 17:08:26 |
| hexa | unstable for me means … watching out for curveballs that arrive via staging | 17:08:57 |
 hab25 | Damn, just realized I shouldn't do this right now because I use home-manager which has specific package version requirements. Therefore, if I use rolling versions for both nixpkgs and hm then I expect would they often become unsynced due to hm lagging behind in updating its modules.
I wish hm were part of nixpkgs =(.
| 17:17:19 |
| K900 | HM master is what you're supposed to be using with nixos-unstable | 17:19:10 |
| K900 | And it works fine pretty much always | 17:19:13 |
| hab25 | Hmm, considering it, again with the safety net of rollback... | 17:22:49 |
| hab25 | It's an easy problem for hm to solve actually, it just needs version assertions, e.g. if the following file had an assert pkgs.alacritty.version == "0.7" somewhere in it https://github.com/nix-community/home-manager/blob/780be8ef503a28939cf9dc7996b48ffb1a3e04c6/modules/programs/alacritty.nix#L14 | 17:24:10 |
| K900 | Applications generally don't break configuration formats that often | 17:25:08 |
| hab25 | * It's an easy problem for hm to solve actually, it just needs version assertions, e.g. if the following file had an assert pkgs.alacritty.version == "0.7" somewhere in it https://github.com/nix-community/home-manager/blob/780be8ef503a28939cf9dc7996b48ffb1a3e04c6/modules/programs/alacritty.nix | 17:26:10 |
| 7 Dec 2025 |
|  Robert Evans joined the room. | 18:46:40 |
| Robert Evans set a profile picture. | 19:02:42 |
| 13 Dec 2025 |
|  NixOS Moderation Bot unbanned  @mightyiam:matrix.org. | 05:59:31 |
| 14 Dec 2025 |
|  suua joined the room. | 13:32:38 |
| 26 Dec 2025 |
|  jappie changed their display name from jappie to jappie @ 39c3. | 15:49:41 |
| 27 Dec 2025 |
| jappie changed their display name from jappie @ 39c3 to jasper @ 39c3 ☎️ 62749. | 13:30:50 |
| 30 Dec 2025 |
| jappie changed their display name from jasper @ 39c3 ☎️ 62749 to jasper. | 23:38:40 |
| jappie | 23:40:10 |
| 4 Jan 2026 |
| jappie changed their display name from jasper to jappie. | 10:59:43 |
| 11 Jan 2026 |
|  ivan joined the room. | 01:55:39 |
|  ghpzin changed their display name from ghpzin (moved to @ghpzin:envs.net) to ghpzin. | 15:04:42 |
| 5 Jul 2022 |
|  zrsk joined the room. | 14:27:26 |
|  infinisil set the room topic to "https://github.com/nixpkgs-team". | 14:29:59 |
| infinisil | Alright, I've heard the suggestion "Nixpkgs Architecture Team" a couple times. I think that's the best name for this team. Other ideas are just "Nixpkgs Team" (too generic) or "Nixpkgs Design Team" (slightly ambiguous what design refers to)
I'll change the name one final time to "Nixpkgs Architecture Team" now :) | 14:35:09 |
| infinisil set the room name to "Nixpkgs Architecture Team". | 15:17:54 |
