| 8 Jul 2022 |
|  Burrito (marius) changed their display name from Burrito (Marius) to Burrito (marius). | 15:24:03 |
 matthewcroughan - nix.how | Alyssa Ross: based on what you were saying about nixos-hardware, does this mean we should be building and caching nixos-hardware? | 17:10:24 |
| matthewcroughan - nix.how | that's the only way I can fathom getting rid of vendor kernels from nixpkgs | 17:10:35 |
 Alyssa Ross | Yeah I think that's a great idea | 17:10:47 |
| matthewcroughan - nix.how | cache.nixos.org would then be able to build and redistribute all vendor kernels from nixos-hardware | 17:11:02 |
| matthewcroughan - nix.how | I think what you're saying about vendor kernels might be premature though | 17:11:24 |
| Alyssa Ross | There are a lot of improvements somebody who wanted to put the effort in could make to nixos-hardware, and that's definitely a big one | 17:11:24 |
| matthewcroughan - nix.how | the reason is because flakes aren't stable yet, and this functionality all relies upon flakes | 17:11:33 |
| Alyssa Ross | no it doesn't | 17:11:38 |
| Alyssa Ross | I've been using nixos-hardware since before flakes existed | 17:11:51 |
| matthewcroughan - nix.how | in practice, nixos-hardware is a flake without legacyPackages | 17:11:51 |
| matthewcroughan - nix.how | it's definitely dependent on flakes as functionality | 17:11:57 |
| matthewcroughan - nix.how | I'm not saying this cannot be expressed without flakes, nor should it, but something to keep in mind | 17:12:08 |
| Alyssa Ross | I don't understand at all the point you're trying to make | 17:12:24 |
| matthewcroughan - nix.how | how people will ultimately use this stuff will be as a flake, since nixos-hardware doesn't have any flake-compat | 17:12:57 |
| Alyssa Ross | you can use nixos-hardware just fine using any of the mechanisms you'd use to evaluate nix code | 17:13:01 |
| Alyssa Ross | I personally use a git subtree | 17:13:06 |
| Alyssa Ross | you could also use niv | 17:13:09 |
| Alyssa Ross | or a channel | 17:13:15 |
