Adam Kennedy wrote: > I'm not suggesting we test against the post-make code, but if we keep > everything, we can be fairly certain we still have any data files or > other things that are needed to support the testing. > > Now we rerun the test suite, but without including blib. > > And you get a full test run against the currently installed code, but > with any data files or other stuff the tests need available.
How are you going to exclude blib? Since the point of hanging onto the source tree is to account for customized installers, they will have customized test harnesses.
