What bothers me about #nixos is the lack of documentation. For example, I can't find how to write bridge and vlan configuration properly. I could add some shell hacks, but then what is the point of Nix in the first place?
@amiloradovsky I'd prefer to avoid having to write anything manually. Adding vlan and bridge configuration support on the other hand would be quite interesting.
@newt @amiloradovsky you can do that with the systemd-networkd support. IIRC that's the only (sane?) way to do it currently.
Since I hyped networkd I started to rethink it.. Its not perfect but we can report bugs and improve it over time.
@andi @amiloradovsky yeah, I suppose translating configuration.nix into networkd config would be the way to do it
@newt @amiloradovsky there are already config options for that: https://nixos.org/nixos/options.html#systemd.network
Some of those are even validate so the amount of invalid configurations you can generate is very limited.
@newt
Yes, the documentation for NixOS is fairly minimal. — Scan `man configuration.nix` and try to utilize as much of the fields as possible.
Shell hacks are acceptable in Nix, but not Guix. For instance, the build tools and per package Nix-expressions often rely pretty heavily on the shell.
The point of using Nix is that it works as a wrapper for all these "contaminated" ("impire") build tools and makes sure the results are reproducible.