| 29 Jun 2025 |
 emily | nixos-facter might achieve it more | 04:33:51 |
 ElvishJerricco | I mean sure but we're not also going to tack that onto the todo list for this | 04:34:06 |
| emily | I don't think it is really bad to expose people to networkd config. that is what they are expected to write on Arch etc. | 04:35:01 |
| ElvishJerricco | That isn't the point | 04:35:10 |
| ElvishJerricco | I don't care if users are exposed to it or not | 04:35:18 |
| ElvishJerricco | I care that what we generated one day is something we can continue to maintain the next | 04:35:29 |
| emily | NixOS can't be in the game of making its own complex abstraction layers for everything in the system | 04:35:32 |
| ElvishJerricco | we can't make changes to generated configs | 04:35:33 |
| ElvishJerricco | we can make changes to abstraction implementations | 04:35:38 |
| emily | I still think hardware-configuration is a red herring here | 04:35:49 |
 hexa | The users that use the unmaintained shit don't maintain the abstractions | 04:35:53 |
| ElvishJerricco | it's literally the only thing nixos-generate-config is about? | 04:36:02 |
| emily | "I want DHCP by default" is configuration.nix not hardware-configuration.nix teritory | 04:36:04 |
| hexa | Whatever we give as a configuration.nix is mutable by default | 04:36:14 |
| emily | and there's no promise that configuration.nix never has to change | 04:36:15 |
| hexa | And everyone manages to enable network manager on their laptop as well | 04:36:29 |
| hexa | or not, idk | 04:36:32 |
| emily | In reply to @elvishjerricco:matrix.org
it's literally the only thing nixos-generate-config is about? it generates a configuration.nix too, does it not? | 04:36:40 |
| emily | I haven't actually run it in years | 04:36:46 |
| ElvishJerricco | I mean if you just want to move all networking stuff out of hardware-configuration.nix altogether that's a different thing. | 04:36:52 |
| hexa | Redacted or Malformed Event | 04:36:59 |
| hexa | Redacted or Malformed Event | 04:37:02 |
| ElvishJerricco | networking.useDHCP = lib.mkDefault true; goes in hardware-configuration.nix | 04:37:27 |
| hexa | sorry, I might be wrong | 04:37:31 |
| hexa | that's stupid to have in hardware parts | 04:37:40 |
| emily | things that aren't hardware config should certainly not be in there | 04:37:47 |
| emily | so that is more reason to change the generator :P | 04:38:01 |
| hexa | if we wanted that to be a default, why not set the default in nixpkgs 😄 | 04:38:12 |
| emily | I guess it actually is hardware-y right now | 04:38:29 |
| emily | because it iterates over /sys | 04:38:36 |
