Subject: Re: Stopping a common shoot-your-own-foot problem
To: Martijn van Buul <email@example.com>
From: Geert Hendrickx <firstname.lastname@example.org>
Date: 03/30/2005 12:27:38
On Wed, Mar 30, 2005 at 12:24:32PM +0200, Geert Hendrickx wrote:
> This could get really difficult. For example: mail/spamprobe is a
> spamfilter which uses db4. It has no config-file, it's just called by
> procmail (or any other mailfilter) with specific command-line arguments.
> It has a default database location (~/.spamprobe/sp_words), but I am
> also using non-default locations ("spamprobe -d $location") because I
> use different databases for different mailboxes. So the upgrade-process
> should go find each users .procmailrc (which can themselves be in
> non-default locations), parse it to try to find out where the users
> spam-databases are, etc... This could get really difficult. :-)
> I much prefer the warning-and-break-unless-some-variable-is-set-method.
Another argument is that I wouldn't like important databases to be
dump-restored with incompatible versions of db4 in an automated way.
I wouldn't mind taking some time to do that manually. :-)