On Wed, Dec 14, 2005 at 04:54:54PM -0800, Justin Mason wrote: > So we have these requirements: > > 1. use /var for updates, instead of /etc or /usr > > 2. sa-update updates must not overwrite any packaged files > > 3. the user shouldn't have to choose at package-install time whether > they want to use packaged rules, or sa-update rules. (although > conversely, it's ok to entirely stop using packaged rules from that > point on, if sa-update installs an update set.)
Agreed. > So the suggestion is to use: > > /etc/mail/spamassassin: > > *.cf > *.pre: Admin-installed local settings > > > /usr/share/spamassassin: > > default, distro-package-installed scores and rules > > > /var/lib/spamassassin/3.1.0: > /var/lib/spamassassin/3.1.1: > /var/lib/spamassassin/3.1.2: > /var/lib/spamassassin/3.2.0: > > sa-update-installed scores and rules I'm not sure I see the need for multiple directories lying around. I suppose it can be useful, I'm assuming that most will only have one directory. Also, sa-update should be smart enough to remove old directories of previous versions (optionally?). > The presence of anything in /var/lib/spamassassin/3.1.1 causes > /usr/share/spamassassin to be ignored. > > All rules, including the code-tied stuff for that release, are put in the > sa-update tarballs (and therefore /var/lib/spamassassin/3.1.2 etc.) Hmm... does it make sense to redistibute the code-tied stuff? That seems like unnecessary bandwidth usage. sa-update should only be grabbing the "changing" non-code tied stuff. -- Duncan Findlay
signature.asc
Description: Digital signature
