I've incorporated the subpackages as you suggested, works flawlessly, thanks again. I've also added an nftables backend, so now there is a subpackage for every firewall backend that both SSHGuard and Fedora support. The package now also builds for el6/7 (minus the subpackages, because RPM in CentOS/RHEL doesn't support suffix-stripping or boolean/weak dependencies yet), but I haven't tested those yet. (For now, this version is in a testing copr repo [1] and in the testing branch of my git [2]). One more question: with nftables and firewalld backends, sshguard does all the fw configuration on its own, for iptables the user has to manually configure some chains/rules. Is this something the package can do automatically on install/uninstall or is messing with another package's config (the firewall, no less) in this way a no go? For now, I'm just printing a message telling the user what to do, but it is a fairly harmless modification: It just creates a sshguard chain that everything gets passed through, all other modifications happen inside that chain, so flushing/deleting that chain should return the fw to its original state. Best, Christopher [1] https://copr.fedorainfracloud.org/coprs/lcts/sshguard-testing/ [2] https://gitlab.com/lcts/sshguard-rpm/tree/testing _______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx
