DevOS | 37 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 | ||
| * so by pulling pkgs from the module args here: https://github.com/nrdxp/nixpkgs/blob/6dbf8c04097c8961bb1cb9cb319fee42eb19ab7a/nixos/modules/programs/zsh/zsh.nix#L288-L293 You are overiding the pkgs you declared in your let binding earlier | 19:13:51 | |
| does home-manager have a way to override the global pkgs? I doesn't look like it from the docs. In that case, it looks like you'd wanna throw your overlay in nixpkgs.overlays | 19:16:17 | |
In reply to @timdeh:matrix.orgThere's an attribute called overlay in the flake schema. I don't put it in there? | 19:18:29 | |
You could do that, and then import it into home-manager by referencing it from self | 19:18:51 | |
| digga's mkFlake does this for you, but if your building from scratch you'd have to wire that up yourself | 19:19:08 | |
so basically the way you have it now, you could just add a nixpkgs.overlays = [ self.overlay ] | 19:19:55 | |
| to your home-manager module | 19:20:06 | |
| That doesn't quite make sense to me. So here's what you're suggesting (correct if wrong)
What confuses me about this is that I'm still using the | 19:26:05 | |
| 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 | |