http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4788
------- Additional Comments From [EMAIL PROTECTED] 2006-02-10 21:12 ------- (In reply to comment #4) > We in particular will not be able to use spamassasin-3.1.1's sa-update if it > puts things into /etc/mail/spamassassin instead of local_state_dir due to > various reasons including SELinux policies. This also is not good because it > does not conform to FHS. FWIW, the current 3.1.0 sa-update puts things in /etc/mail/spamassassin. > Why not use versioned local_state_dir? Wouldn't doing this upon initial > production launch of this capability in 3.1.1 minimize future migration issues > and keep things inform? The main issue is that in 3.2 (and with the patch in this ticket), local_state_dir overrides def_rules_dir, which won't work with the way 3.1 currently does things (come to think of it, it may not work in 3.2 either... have to investigate.) It's also, as jgm points out, a relatively major change to 3.1 since it actually touches and changes the behavior of the main code. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
