On Fri, Sep 24, 2004 at 02:37:31PM -0400, Kris Deugau wrote: > Justin Mason wrote: > > Yeah -- this is almost definitely something to do with SuSE's > > packaging of either perl (if it uses the defaults from > > ExtUtils::MakeMaker) or SpamAssassin itself (if its rpm spec moves > > the file around as Debian does). > > Actually, for any "real" package manager (ie, rpm or dpkg), upgrading a > package should remove all old files as a part of the upgrade.
The issue related to SuSE is that previously, one has been able to install the SuSE default .rpm package, and then subsequently upgrade using cpan without removing the old package first since the old binaries and entire contents of /usr/share/spamassassin/ have been overwritten by that process. SuSE are unlike Debian (for instance) in that they don't release (with one or two exceptions) upgraded packages other than to address security vulnerabilites, so to upgrade to a more recent version of any particular application cannot generally be done with a SuSE .rpm. For those that primarily maintain and administer their system using YaST, manual configuration of startup scripts etc is also somewhat difficult so it can be of benefit to rely on SuSE's copy of /etc/init.d/spamd - for example, the one recommended in spamd's README.SuSE file doesn't actually work, on SuSE 8.2 at least. So, installing the default SuSE .rpm that came with one's version and then subsequently upgrading one's SpamAssassin using cpan has benefits there too. -- Anthony Edwards [EMAIL PROTECTED]
