I've been looking into a build w/out IPv6 support as well. I started a list of packages installed by default (on my Netgear R6100) that I think are IPv6-related:
I am little bit concerned, anyway, as last time I tried it with OpenWRT I ended up with an unusable box!
In regards to the original "suggestion" I wouldn't strip all related elements to iptables and dhcp servers, though.
Having a WAN with DHCP client or a LAN with a DHCP server is too common to ditch it!
I think that the "trimming list" needs some major rework.
The only thing is that I cannot get rid of luci-proto-ipv6 and luci-proto-ppp despite I am asking explicitly to exclude them. There needs to be something requiring them back.
Any idea?
Thanks.
If I don't install luci-ssl and just luci, I don't get luci-proto-ipv6 and luci-proto-ppp pulled in.
So it could be that it's luci-ssl to depend upon luci-proto-ipv6 and luci-proto-ppp ...
Where are those dependencies recorded?
In the package source?
I have to keep luci-ssl and can ditch luci-app-commands luci-app-watchcat.
So I rebuilt the image but I sill get both libip6tc and luci-proto-ipv6 pulled in for about 22Kb or storage.
I think that luci-ssl shouldn't rely on the these two packages if all other IPv6 stuff has been disabled.
Both luci and luci-ssl are empty meta packages that depend on a number of components for easier installation. If you omit luci-ssl and/or luci you can freely deselect components like luci-proto-ipv6.
I will try a little bit harder...
It ain't easy.
Maybe the IPv6 stuff should be packed together in a few separate packages. But this seems to be another story.
That CONFIG_IPV6 switch is in the kernel configuration.
That wouldn't stop the IPv6 packages to be pulled in, anyway.
Disabling IPv6 in the kernel would save some room, indeed.
But the trick is clearly in the package dependencies: those should be modified.