NixOS Module System | 180 Members | |
| 38 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Jul 2025 | ||
| Something I'd already tried earlier but discarded due to an unrelated error (that I thought told me I could not do things this way):
So yeah, the inner | 07:14:28 | |
| x10an14: taking the discussion from the beginning … If you want to declare options specific to one instance, you can do it as follow:
If you want to make the | 09:36:22 | |
If you want your option to define home-manager.<user> from foo.<user>, unfortunately there is no simple shortcut that exists today, you will have to fallback to the nix language / Nixpkgs library to map the attributes of one into the other. | 09:39:25 | |
| nbp: Thanks! =D I got it to work, as described in the previous 2x messages of mine =) Any feedback/suggestions welcome! | 10:29:35 | |
| x10an14: This is the right channel. Thanks for the link, I was not aware of the pipe operator. | 12:03:29 | |
| Aight, and yw =) | 12:07:17 | |
| 25 Jul 2025 | ||
| 12:11:00 | ||
| 31 Jul 2025 | ||
| 00:25:28 | ||
| 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 | |
| There's plenty of examples in Nixpkgs. Did you find some? | 06:42:08 | |