http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5147





------- Additional Comments From [EMAIL PROTECTED]  2006-10-26 09:04 -------
(In reply to comment #2)
> Alternatively, dev versions could include the revision number in the updates
> ruleset path... /var/lib/spamassassin/3.002000-r123456/.

(In reply to comment #4)
> actually, I think Daryl's suggestion is probably neatest...

The issue is: what is r123456 ?  The version of sa-update?  Only changes when
sa-update changes.  The dev version in M::SA?  Only changes when M::SA is
updated.  Checked out revision you built from?  Would require kluges to work
(likely the same type of kluges as our nightly/weekly runs do).

I still think the already suggested behavior of running sa-update after doing an
install/upgrade is the best solution.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to