Hi.

Well I've already mentioned that in the other bug.

IMHO, the nftables package itself shouldn't contain any
logic/init-scripts/units for loading/unloading the rules.

Debian already has the netfilter-persistent package for that
task, which by itself is indepentend of the backend used, so
e.g. for iptables rules, there is another package
"iptables-persistent" which provides the necessary hooks for
netfilter-persistent to do the loading.

This would have several advantages:
- code not being duplicated
- using an existing (more powerful) framework
- other init-scripts/unit-files which generically need to
  depend on firewall loaders wouldn't need to add yet another
  service name to their lists
- more homogeneous and configurable handling of the task among
  the different debian packages (i.e. "iptables" does not
  provide such rules loaders, while "nftables" does)


Cheers,
Chris.