Olivier Nicole wrote: ON> > The tricky part is maintaining a list of which rules will work only in CVS vs ON> > which rules are OK for the nightly distro. ON> ON> I beleive regexpr are stand alone.
Not always -- for example when "rarebody" gets added as a regexp type. ON> I beleive most eval are. Well, they all at least depend on EvalTests.pm -- but of course we could distribute that. ON> Other could start with a version check of the SA engine. Version check ON> being build in once and for ever in the rule. So say you add a new "rarebody" rule -- are you going to go back and check which version "rarebody" first worked in? And is that version number the SA release number? In which case say rarebody goes in before 2.30 -- the release number would be 2.21 (current CVS) -- but it won't work with "old" 2.21, only new 2.21. So do you instead use the CVS version number? If so, then of which file? I think a dependency system would probably just create more complication than it'd be worth. I think the better option would be to have the nightly build script check the current rules against the most recent stable release, and check which rules fail, then remove those from the nightly-rules.tgz distro. C _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
