| 31 Jul 2025 |
|  Sammy (It/Its) left the room. | 10:02:52 |
 unwary | I did not, or did not detect it. I seemed to examine modules that used various build-wrapping tools that I presumed handled that as part of the build. | 23:53:39 |
| 1 Aug 2025 |
 @mightyiam:matrix.org | Sorry for not being clear. It's not in a NixOS module typically, but in the package for some piece of software. And might not be obvious. The part of this that is in the NixOS module is that the package of the software ends up in environment.systemPackages and includes the .desktop file. | 06:32:42 |
|  yan 💕 joined the room. | 15:42:19 |
| 5 Aug 2025 |
|  isabel changed their profile picture. | 09:49:13 |
|  Axel Karjalainen joined the room. | 18:48:14 |
| 6 Aug 2025 |
|  vidariondr set a profile picture. | 18:31:00 |
| 7 Aug 2025 |
| @mightyiam:matrix.org | https://discourse.nixos.org/t/nixpkgs-module-system-config-modules-graph/67722?u=mightyiam | 16:53:44 |
 nbp | Let's see how much time it take before someone ask what is the difference between key and file. | 17:05:23 |
| nbp | Now people might understand why you should not write a NixOS module within a flake, because it lacks position information.
{agenix, ...}:
{
# Using the module directly prevent the deduplication from working properly.
imports = [
agenix.nixosModules.default
];
}
| 17:11:50 |
| nbp | * Now people might understand why you should not write a NixOS module within a flake.nix file, because it lacks position information.
{agenix, ...}:
{
# Using the module directly prevent the deduplication from working properly.
imports = [
agenix.nixosModules.default
];
}
| 17:12:41 |
