https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7397
--- Comment #8 from Michael P <[email protected]> --- Before I set out to complete this, as mentioned I would like a little feedback. I propose changing sa-update to sa-update-local and sa-update-remote. 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. Package Maintainers can ensure that sa-update-local is run on installation, but that cron jobs run sa-update-remote. I would also suggest that we deprecate support for older GPG, package maintainers for new versions of SA should ensure that the latest is being used. I also propose that going forward ONLY the channels.d configuration be used, rather than the older method of accepting just a single channel file structure. This way, the 'import GPG key' funtionality could also be removed from sa-update-remote. Updated GPG keys should really only be provided by package maintainers. Please provide comments, if you disagree, as this is the direction I would like to head. By shipping sa-update-remote as a 'new' script, it will also help ensure a simpler migration path. -- You are receiving this mail because: You are the assignee for the bug.
