On Wed, Mar 10, 2004 at 11:23:22AM -0800, Justin Mason wrote: > How's about a config setting for "support upgrading from v0/v1 dbs", > defaulting to off?
Unnecessary since we're not talking about upgrading. :) > What I'd hate is to have to say to someone: "you need to install > SpamAssassin 2.63, run a command, then install SpamAssassin 3.0.0 > over that and run another command". I've run into products > that do that, before, and it's a world of pain for users. No no no... Upgrading would still work, but using the old DB for check() and dump and such won't (it currently does) -- our upgrade process is "upgrade on first write", which is why we recommend people do "sa-learn --rebuild" after they upgrade (and optionally do the --import if they have to...) -- Randomly Generated Tagline: "If you're running the latest version of IIS, then you're not vulnerable to this [security hole], but you're vulnerable to something new." - Phil Cox
pgpQWckP1VAmU.pgp
Description: PGP signature
