http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4952
------- Additional Comments From [EMAIL PROTECTED] 2006-08-13 16:12 ------- Ok, updated rules have to be in var; fair enough. But then that begs the question, should the SA installed rule base get installed into var in the first place? Rather than being installed one place and then, to the mystery of many, completely overridden into another place on the first sa_update? One can argue, "well, some people might not update it so for them it isn't variable". One can argue "traditionally it hasn't been there, so moving it would be a surprise". (And it seems that it is, since it not only moves, the name changes.) One can argue "there are lots of legacy installations where it is somewhere else before the first sa_update run". There are lots of considerations and arguments, and I just have this feeling that not all of the possibilities have been considered or argued completely. Perhaps the soltution should be, not to add another directory to the default rules path, but to outright move an existing directory. For instance, there could be an sa_update_install that would move the system rules (that are going to be replaced anyway) out of lib/xxx or wherever they are into /var/spamassasssin/rules or the like, delete the old directory, and install a link to the new directory to eliminate confusion for the first few months. Maybe install a Readme file in the directory describing why and where the directory moved. Installing a link would help eliminate initial administrator confusion, and possibly program confusion if there is non-SA stuff that is looking in or for the moved rules. Having an sa_update_install program (rather than having magic happen on the first sa_update run) would notify admins that something is going to change in the way things work. It would also eliminate (perhaps trivial amounts) of code from sa_update itself. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
