On 23 July 2015 at 12:32, Michael Biebl <[email protected]> wrote: > Am 23.07.2015 um 13:21 schrieb Dimitri John Ledkov: >> If we in-vision that networkd is / will-be required on minimal >> systems, I would want to have an alternative build available of >> networkd & nspawn with firewall support enabled. (could be something >> like update-alternatives, or e.g. systemd-networkd-firewall.service >> that conflicts with normal networkd units or whatever.) > > I think it would be highly confusing to have two builds of > systemd-networkd with different feature sets and bringing > update-alternatives into the mix wouldn't help. So I'm not sure we want > this. >
So split networkd into stand-alone package, and enable iptables-dev dependency. It's not enabled by default service, is it? Thus should not be installed together with init, given the deps it wants / pulls in. And from the bug reports there is clearly demand for full functionality to be available from networkd. Looks like win-win, minimal install is kept minimal, yet optional component is fully featured. -- Regards, Dimitri. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
