> I'd like to see if there's a way to combine the two somehow so that new
> SVN commits that update sandbox rules, are immediately mass-checked alone.
> However, I can't see a way to do that reliably from SVN commits alone,
> because (for example) meta rules may depend on other rules that were not
> changed as part of the same commit. So I think the "email with attached
> rules file" is still a better model.
I may be wrong here, but isn't an svn commit commiting a changed file? If
so, I'd expect the whole changed file to be picked up and mass-checked, not
just a diff from a previous version.
Of course, this kinda implies that the user has a testrules.cf file that
contains just the rules he wants tested at the moment, and keeps
recommitting it (or them, if he has multiple test files) every time he wants
a one-off masscheck.
At some point the user might like the results of some/all of the checked
rules, and then commit them to another fullcheck.cf file. This would be
some key name or different subdirectory, and would thus key that it is
intended for a full masscheck, possibly with a one-off in addition.
Loren