> I *think* what Daniel was thinking of here, which should work, is > just using the "ifversion" commands to conditionalize too-advanced > rules.
Assuming ifversion can be used in the negative also. For instance, we have one set of meta rules that use addition post-whatever, and do a less-good job using || pre-whatever. So it isn't necessarily just dropping rules out of older versions, it can be supplying version A for one release and version B for another release. Also, I seem to recall (perhaps incorrectly) that ifversion only came into existance not that long ago, and didn't work quite right or wasn't present in the 2.5-2.6 timeframe? 2.5 is probably uninteresting at this point, but half a century of doing commercial software has taught me that you support one major release back, which I would probably deem to be 2.6x.
