http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4952
------- Additional Comments From [EMAIL PROTECTED] 2006-08-13 14:54 ------- Apologies, it wan't meant that way. I meant what I said - at times when every time I fix something something else comes up and causes an 'oh darn', it sometimes helps to just take a step back and a deep breath and say: "Ok, is there some other way to get the result I want? What result am I *really* trying to achieve? A lot of the time I realize I wasn't really trying to solve the right problem in the first place, and that was why solutions kept having problems. Maybe that doesn't happen for other people; except that I know it has happened a few times over the years with other people I've worked with, as well as with myself. Maybe they were unique and I'm being presumptious that it might ever happen with someone else. Now, maybe that isn't the case here. Maybe there isn't any other solution to the problem. But as I read over this rather long history of things here, that start with the comment in #2 of "trivial patch" and go on getting more and more complex from there, I have to think: waitaminute, there is somethinng that doesn't seem right here! I personally don't have a solution, trivial or otherwise. I wish I did; I'm sorry, I don't. But what my mind is telling me as I read this patch history is: "Maybe the problem here isn't how to get local_state_dir to work. Maybe the problem *IS* local_state_dir". I keep wondering: how would we solve this problem if local_state_dir didn't exist? Would the solution be simpler? Now, maybe that isn't the right solution either. But I can say that if I were working on this, about now I'd be taking a step back and asking myself if that might be the right solution. And I'd doubtless be considering two or three other completely off the wall possibililties also. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
