http://bugzilla.spamassassin.org/show_bug.cgi?id=4314
------- Additional Comments From [EMAIL PROTECTED] 2005-05-10 20:19 ------- Subject: Re: Determine how to merge init.pre files from release to release [EMAIL PROTECTED] writes: > http://bugzilla.spamassassin.org/show_bug.cgi?id=4314 > > > > > > ------- Additional Comments From [EMAIL PROTECTED] 2005-05-10 19:32 ------- > OK, I think the best bet is to move to a "v310.pre" model -- in other words, > leave init.pre exactly as it was for 3.0.x, don't overwrite a user's version > of > that file, and instead put additions into v310.pre. > > each release that adds a plugin needs to add a new "vXYZ.pre" file to load > that > plugin and any other new ones. (hopefully most releases won't add plugins > that > often.) > > deletions of old loadplugin lines from old files: can't think of an easy way > to > do this -- maybe just leave the plugin code as a no-op, and if the user is > still > loading that file, they just won't get any results from it. > > The alternative? we write a script that does stupid diff and patch tricks. > nein danke! > The issue I have with this is that things like Razor depend on init.pre now and did not before. So, when upgrading, if you don't pay attention, you lose functionality. However, this isn't the first time that upgrading required doing some "housekeeping" to make things continue to work the way they did as with the previous version. Perhaps just documenting this clearly in the UPGRADE file??? - Paul - ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
