On Mon, Nov 24, 2008 at 10:37 PM, James Keenan via RT <[EMAIL PROTECTED]> wrote: > 1. Attached find a list of files containing 'miniparrot'.
This list is much smaller in the 'rm_miniparrot' branch (basically restricted to t/) > 2. In most cases, you can work on a config/*/*.pm file and the > corresponding t/steps/*.t file together. Since the 'miniparrot' option > tended to short-circuit the workings of a particular config step's > runstep() method, the test for 'miniparrot' usually appears early in the > test file. config/ has been cleaned up in branch, as far as I can tell, and all tests (aside from the configure tests) pass. If you could fixup one of the steps tests in branch, I can probably apply that to the remainder of the tests. I can't tell which bits in the miniparrot section are just for miniparrot, and which are there because it happens to be the first section of the test. Thanks. -- Will "Coke" Coleda
