| 12 Oct 2025 |
 John Ericson | If you grep for DaemonVersion I think you'll see it | 14:05:28 |
 justinrestivo | Hello! Any chance there's a spec about the different Fields provided for each ActivityType in the nix logger? Right now to answer this question I'm grepping the nix codebase for each ActivityType and looking at the arguments to the Activity::Activity constructor to infer the field types and number (if any exist). I'm wondering if there's an easier/more canonical way to do this. | 15:30:35 |
 midischwarz12 | You overlay when you want to stitch multiple overrides together or want the package that's available across your entire package set such as nixpkgs. What you're really desiring is just a single override and probably not overriding every package that consumes this package as a dependency. So an overlay would be unnecessary | 16:39:36 |
| midischwarz12 | * You overlay when you want to stitch multiple overrides together or want the override available across your entire package set such as nixpkgs. What you're really desiring is just a single override and probably not overriding every package that consumes this package as a dependency. So an overlay would be unnecessary | 16:40:03 |
| midischwarz12 | * You overlay when you want to stitch multiple overrides together or want the override available across your entire package set such as nixpkgs when used as a dependency. What you're really desiring is just a single override and probably not overriding every package that consumes this package as a dependency. So an overlay would be unnecessary | 16:40:25 |
| midischwarz12 | I think overlays are often reached for a bit too early and people should take note more often that this ruins a lot of the reproducible nature of nix. Your nixpkgs will no longer be the same as everyone else's when you use an overlay | 16:41:25 |
 Sergei Zimmerman (xokdvium) | Adding builds with ASAN/UBSAN to hydraJobs: https://github.com/NixOS/nix/pull/14227 | 16:59:48 |
