[EMAIL PROTECTED] wrote:
OK, now after reading the whole INSTALL file, I come to the conclusion that to upgrade, one just acts like one never installed SpamAssassin in the first place, and apparently the new SpamAssassin will just install on top of the old one (with cruft surely accumulating in the corners, I bet.)
This is why I don't often install from source. I install distribution packages, third-party packages, or my own local packages (in that order of priority). There's also the slight issue of keeping the build process as identical as possible between systems if you're installing on a cluster of some kind.
Things still get a little messy around the edges after a couple of years, but packaged software reduces that by quite a bit IME.
On the SA cluster at head office, I've taken a slightly different tack; I wrote a couple of short shell scripts to ease SA upgrades. (Those scripts, incidentally, are packaged locally. <g>)
One snags the tarball and installs it to a unique location based on the version number it's passed as a command line argument.
The other rearranges symlinks and restarts SA to switch the running versions.
I'm still left to make sure the full config gets copied over from the current install to the new one, but that also *forces* me to review any customizations I've made. For instance, we disabled a couple of RBLs a few releases back because they started triggering on everything, and the release we're running has those removed completely - no point in keeping the "score BADRBL 0" lines around.
-kgd
