Its support is very experimental upstream and things break. For e.g. user-level
services just don't work, and have no way to know/fix it. NixOS-WSL maintainer
is not very keen on working around that because of complexity and because
upstream is better place to fix it. As such, and on his advice, its better to
stick to the original state of affairs.
By removing minimal.nix config.noXlib is not set, and includes some other
packages per matrix answer.
But it will allow gtk to build and the rest of the system can now be updated.
While I can setup dhcp with bridged networking on WSL, it won't be as friction
free. I'll have to setup a bridged adapter with same name in Hyper-V and then
the imperative state starts accumulating again.
Not fun.
I might have hardcoded hotsts file, which would have had been alright with my
threat model, but I realised only reason I want my DNS is privacy and
ad-blocking. But since neither browser nor any nefarious applications (at least
I hope not) run from within the VM, oit doesn't make sense.
Now the only thing remaining about this is that broken scrobbling in navidrome.
In that case, oh well.. not like all the client applications are fun, so might
as well live with it.
By default WSL generates the hosts file, but since NixOS can do its job, its
better to let it. Previous hosts file must be deleted first for this to take
effect.
resolv.conf generation via NixOS is currently disabled, but I might just do it.
DHCP is disabled so I'm not sure what else needs to be applied, but we'll see.
