15:37 <arianvp> Big brain idea: Make systemd.networks a list; instead of an attrset

15:40 <Mic92> I prefer a set because you can than overwrite existing networks.

15:40 <Mic92> Filtering a list is harder

15:40 <arianvp> you can still override existing ones

15:40 <arianvp> https://pastebin.com/KmNhqALp

15:40 <arianvp> the first number always matches in networkd; nothing is merged

15:40 <arianvp> so you'd just `mkBefore` your thing you want to override

15:40 <arianvp> and make an appropriate Match

15:41 <arianvp> e.g. systemd might ship with a `99-default.network` that matches Name=ens*

15:41 <arianvp> but you could then just networks = mkBefore [{Match.Name="ens*"; Network = { ... my overrides }; }]

15:41 <arianvp> but yeh that means you cant _customize_ existing ones; only override them

15:42 <arianvp> Due to networkd "units" not really being units; but really a list of match rules; I think it's neat

15:42 <arianvp> and a bit more honest

15:43 <arianvp> same goes for tmpfiles rules for example

21:46 <andi-> how does that override thing merge the configs? based on the match? I think it isn't a great idea.