http://bugzilla.spamassassin.org/show_bug.cgi?id=4314
------- Additional Comments From [EMAIL PROTECTED] 2005-05-10 21:01 ------- Subject: Re: Determine how to merge init.pre files from release to release /me grumbles. I swear I put something in last night about an idea quinlan and I came up with on IRC. We introduce a new config option, unloadplugin or deactivateplugin or whatever we want to call it. I already added support to parse multiple .pre files. We modify the install process to always install the init.pre file in the share directory, under the theory that it would never be changed. Then if people wanted to turn off a plugin that is in init.pre they can add a local.pre to the site config directory with an unloadplugin. Then while parsing the config we delay loading the plugins to after the .pre files have been completely parsed. Once the .pre files have been parsed, an unloadplugin directive (in a .cf file) would just unregister the plugin, it will still be loaded into memory. One issue we would need to work out is what to do at install time for existing 3.0 configs. But as others have said, maybe it's just something for UPGRADE and leave it up to the user to handle. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
