On Mon, Feb 28, 2011 at 6:03 AM, Royce Williams <royce.willi...@gmail.com> wrote: > For future-proofing purposes, would it be feasible to enable > optionally tagging a signature with its minimum supported ClamAV > version?
Given that this would represent a db change that has its own compatibility issues, would it be feasible to have a "tag field" that let you express things like: min:0.98.1;max:0.98.8;64bit:yes; This would allow for something extensible, like using TXT records for SPF, etc. -- in that it lets future development tag records arbitrarily, and let future versions branch on each tag if needed, and ignore any unrecognized ones ... all with only a single change to the record format. Royce _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
