| 25 Jul 2025 |
| hsjobeki joined the room. | 12:11:00 |
| 31 Jul 2025 |
| unwary joined the room. | 00:25:28 |
unwary | This might be the wrong chat, but I'm trying to understand how to package something like a .desktop file so that a module I write will be included in start menus and such. Right now, enabling my module gets me the executable available on the command line, but as it's a GUI program, that's suboptimal. | 00:26:59 |
@mightyiam:matrix.org | There's plenty of examples in Nixpkgs. Did you find some? | 06:42:08 |
@mightyiam:matrix.org | And yes, this isn't quite the correct room. | 06:42:25 |
| @sammy:cherrykitten.gay joined the room. | 09:35:10 |
| @sammy:cherrykitten.dev 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 |