http://bugzilla.spamassassin.org/show_bug.cgi?id=4314
------- Additional Comments From [EMAIL PROTECTED] 2005-06-01 15:38 ------- Subject: Re: Determine how to merge init.pre files from release to release On Tue, May 31, 2005 at 07:09:08PM -0700, [EMAIL PROTECTED] wrote: > OK, here's an implementation of the "v310.pre" proposal. this is 100% > check-in-able and resolves this bug, but since there's some disagreement I'd > prefer to put it here for comments and/or votes. so have at it ;) > > I'm not attached at all to the "v310.pre" filename btw -- suggestions are > welcome... +1 I think this is the cleanest of the available options for now, given that we need to keep supporting the site config location for *.pre. In the long run, having the multiple pre files seems a bit klugy, especially as we keep adding in more plugins over time. So for 4.0 I'd like to see something like: put the plugin pre file(s) in the standard rule dir, and let the admins (de)activate via their own site config pre file. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
