https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7397
--- Comment #13 from Michael P <[email protected]> --- Expect a flurry of comments over the next few days, unless you think there is a better place to discuss these things instead of in the bug ticket itself. sa-update has code to try and figure out which version of SA is running, and then alter it's behavior based on that. I don't get it. Should not it simply have the same version as SA itself defined at make time, and one simple safety. If the version is not the same as the installed SA version, refuse to run? The decision should be, is sa-update a part of SA or not? Does it not get updated with each SA version? Eg.. # set debug areas, if any specified (only useful for command-line tools) $SAVersion =~ /^(\d+\.\d+)/; if ($1+0 > 3.0) { $opt{'debug'} ||= 'all' if (defined $opt{'debug'}); } else { $opt{'debug'} = defined $opt{'debug'}; } I would assume that if the sa-update matches the installed and running SA, that it would only have code for the running version, correct? Can I deprecate things like this, and assume that we are only writing for the current version? -- You are receiving this mail because: You are the assignee for the bug.
