hexa- changed the topic of #nixos-on-your-router to: NixOS on your Router
Guanin has quit [Remote host closed the connection]
pie_ has quit [Ping timeout: 252 seconds]
pie_ has joined #nixos-on-your-router
pie_ has quit [Client Quit]
THFKA4 has quit [Ping timeout: 250 seconds]
THFKA4 has joined #nixos-on-your-router
<andi-> Finally got around to write nixos tests for my upcoming migration to NixOS on the local router... Should update the networkd module.. Things like the `[DHCP]` section are just legacy and not even documented anymore. (It is now `[DHCPv4]` and `[DHCPv6]`).. Hope to get home soon enough to fix that during the weekend.
<gchristensen> yay!
<andi-> gchristensen: given that all the networkd documentation is written in docbook xml. Do you think it is feasible to generate list of accepted options per section? As a user I love the config "verification" we do in NixOS.. As a developer I hate updating these details…
<gchristensen> +1
<gchristensen> link?
<gchristensen> with munging, yes
<andi-> We obviously can not parse (all) the valid values for options but it seems like it wouldn't be to hard to get a list of options. Even if we just diff it against what we have right now.
<gchristensen> even some simple xpath could extract a lot of the <term><varname>Type=</varname></term> bits
<andi-> I guess my real question was: Is there some docbook magic for that besides the standard XML tooling :)
<gchristensen> ah
<gchristensen> docbook is a lot like s-expressions. they aren't special except for the transformation you can apply to it
<gchristensen> I don't know of anything special here that would answer this question specifically
<andi-> kk
mmlb3 has quit [Ping timeout: 258 seconds]