| 20 Apr 2026 |
 eveeifyeve | What time is nix-meeting? | 16:03:12 |
| eveeifyeve | * What time is nix-meeting start I forgot? | 16:03:21 |
| eveeifyeve | * What time is nix-meeting start, I forgot? | 16:03:58 |
| eveeifyeve | * What time is nix-meeting start? I forgot. | 16:04:07 |
|  raf joined the room. | 16:11:47 |
 Lisanna | 12pm eastern on Monday, 3pm eastern on Wednesday | 20:41:05 |
| Lisanna | https://calendar.google.com/calendar/u/0/embed?src=b9o52fobqjak8oq8lfkhg3t0qg@group.calendar.google.com | 20:41:49 |
| 21 Apr 2026 |
|  miro joined the room. | 00:54:01 |
|  brainlesslukas joined the room. | 04:43:16 |
| 23 Apr 2026 |
|  @richc:corbet.ch joined the room. | 06:47:17 |
| @richc:corbet.ch | I am sorry to interrupt. Hi guys and girls =)
Can I ask you about some indication what nix package manager is the best for getting up to speed quickly on a non NixOS distribution? (Specifically CachyOS, Arch based). Can you go wrong with the standard pacman package or should you choose differently? If I want to be flaky, do I belong in the Determinate Systems corner (Gemini is convinced I need this one) ... and on github I saw there is a legacy installer and a modern one which however seems to be a fork of the Determinate Systems one ... Well, does that mean it has all the features that determinate system advertises and DS is now obsolete?
I am sorry, I admit I am a noob here, but I want to learn and not make a beginners mistake at the ... beginning. | 06:53:49 |
 K900 | The standard Arch package is fine | 06:54:44 |
| K900 | Also you probably want #Nix / NixOS for user support | 06:54:57 |
| @richc:corbet.ch | Heading over there in a sec. Thanks @K900 for the quick answer. | 06:56:34 |
| 24 Apr 2026 |
|  @onatustun:matrix.org left the room. | 21:49:35 |
|  onat joined the room. | 21:59:04 |
| 25 Apr 2026 |
 Mic92 | https://github.com/NixOS/nixpkgs/pull/513339 nixpkgs cleanup (2.28 and 2.30) | 11:12:32 |
| 27 Apr 2026 |
|  Ninja joined the room. | 14:37:16 |
 ris_ | does nix have a changelog-style document anywhere intended for people developing against the c++ api? something that would give us guidance about what to do about api changes and deprecations | 18:19:03 |
| ris_ | context - nix-heuristic-gc has fallen behind and i'm being told there are 3 ways it is broken by 2.31 in https://github.com/NixOS/nixpkgs/pull/513339 | 18:20:10 |
| ris_ | * context - nix-heuristic-gc has fallen behind and i'm being told there are 3 ways it is broken by 2.31 in https://github.com/NixOS/nixpkgs/pull/513339 | 18:20:27 |
 Sergei Zimmerman (xokdvium) | There's the not so greatly maintained C++ doxygen, we should probably start deploying it somewhere it make it prettie/more readable | 18:21:02 |
| Sergei Zimmerman (xokdvium) | * There's the not so greatly maintained C++ doxygen, we should probably start deploying it somewhere it make it prettier/more readable | 18:21:09 |
| Sergei Zimmerman (xokdvium) | * There's the not so greatly maintained C++ doxygen, we should probably start deploying it somewhere and make it prettier/more readable | 18:23:36 |
| ris_ | hmm... doxygen isn't always more useful than just reading the source, i'm more interested in seeing the active changes and the thinking behind them. e.g. if foo is going away, what is it replaced by? | 18:23:50 |
| ris_ | should we be doing bar instead? | 18:24:11 |
| Sergei Zimmerman (xokdvium) | Hm is there such a case with niix-heuristic-gc? | 18:25:24 |
| ris_ | i haven't looked very deeply into it yet | 19:19:46 |
| ris_ | this was my first port of call to see if there's an easier way than reading loads of source & unearthing PRs | 19:20:39 |
| Sergei Zimmerman (xokdvium) | I can probably help out with the bump | 19:38:37 |
