https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7397
--- Comment #11 from Henrik Krohns <[email protected]> --- (In reply to Michael P from comment #8) > There > are uses for SA to be able to take local copies of rulesets, and activate > them, eg on first installation, for testing/debugging, and in cases where > there is a cluster, and only one system downloads the rulesets for other > systems to use, but the purpose differs enough from downloading rules from > remote mirrors, that they should be different. This would also ensure that > the code is more maintanable going forward. How does this differ from already existing sa-update --install command? Nothing prevents package maintainers from already doing all this. Or clusters doing this. Or local networks rsyncing locally whatever they need. Code being more maintanable is non-issue, since it can be always rewritten if someone wants, but I don't see any need to change the semantics how sa-update works right now. Except the new optional --channels.d operation that would use a new directory structure for configuration. There is no reason to break backwards compatibility for something that works quite fine as it is. -- You are receiving this mail because: You are the assignee for the bug.
