DevOS | 39 Members | |
| Seeking help and geeking out together on https://github.com/divnix/devos & https://github.com/divnix/digga | 10 Servers |
| Sender | Message | Time |
|---|---|---|
| 12 Aug 2021 | ||
| That's what nixpkgs.overlays does under the hood | 19:26:59 | |
so nixos has a nixpkgs.pkgs option where you can just build the global pkg set and it will be passed in to every module. Home-manager doesn't seem to have this, but it does have nixpkgs.config and nixpkgs.overlays, which would be applied to the underlying package set and passed in to every module as pkgs | 19:27:56 | |
I get dependency injection but this seems convoluted. It also seems purely conventional - its' just convention that the prop called nixpkgs.overlays gets picked up by home-manager, applied to nixpkgs, and the result is passed to each module, right? | 19:30:35 | |
| Am I missing a piece, or is it something I get used to as I go along? | 19:32:27 | |
| I still don't understand how to add profiles/suites to a home.users.<user> in flake.nix, | 19:32:53 | |
| are you already familiar with how to use them for nixos? it should be basically the same | 19:34:22 | |
In reply to @ultranix:matrix.orgI'm not sure if this example would be helpful to you but here's I'm doing it https://github.com/d4hines/devos/blob/hope/flake.nix#L103 | 19:34:26 | |
In reply to @timdeh:matrix.org The wiki lists
| 19:37:06 | |
| https://nixos.wiki/wiki/Flakes#Output_schema | 19:37:21 | |
| Oh, it's an attribute of the output object | 19:38:08 | |
oh yes, I didn't notice that. The top-level attributes in a flake.nix should only be description inputs outputs and nixConfig. | 19:39:52 | |
| 19:40:08 | |
outputs being the meat of it | 19:40:11 | |
| i'm getting this with latest nixpkgs-unstable | 19:40:17 | |
| i guess the patches are out of date now | 19:40:24 | |
| I think the patches are only for the nix in the shell though right David Arnold (blaggacao) | 19:41:01 | |
| I just updated nix to master since I recently merged a version bump and it's working on my system. Even with nix-dram applied | 19:41:34 | |
| hmm | 19:41:49 | |
| i think i can build the system fine | 19:42:19 | |
| its just the devshell | 19:42:23 | |
In reply to @d4hines:matrix.orgI empathically understand the impetus. However, if you ask me, it might be easier the other way round.. 🙂 | 19:44:06 | |
In reply to @ultranix:matrix.org if you are using master, you should have some suites under
where the above pulls in a suite I have called | 19:44:36 | |
In reply to @yusdacra:nixos.devyeah, it's just used in the shell because of the follows bug. Hopefully they merge that PR soonish so we can remove the patches all together | 19:45:51 | |
In reply to @ultranix:matrix.orgyou might also have a complementary look at: https://github.com/divnix/digga/tree/main/examples -- they are very minimal. | 19:46:35 | |
| i was not aware digga had that section, nice | 19:48:06 | |
| thanks. some of the examples had removed home-manager.users.<user> from the users/<user>/default.nix and replaced it with just the username. so its confusing | 19:48:07 | |
In reply to @d4hines:matrix.orgflakes only have a weak schema. some attrs are better known than others. any attribute is fine. none has magic semantics beyond a bit of cli ux sugar | 19:48:25 | |
In reply to @ultranix:matrix.orgyeah first I was looking in digga/devos for an example like how I manage my own users, and found the default root/nixos users don't do it like I do | 19:48:52 | |
In reply to @blaggacao:matrix.orgyes but this is only true for the outputs schema. An unexpected attribute in the top-level will result in an evaluation error | 19:49:21 | |
In reply to @yusdacra:nixos.devIs that the follows patch? -- let me know.. | 19:49:40 | |