Huh? Who said anything about a giant harness? Because I can add one line to Build.PL and Module::Build generates a ./Build file that inserts a path in @INC, that counts as a giant harness?
I did. Because having to use bash -c'cd .. ; ./Build test' to run a single test is not right. It runs all the tests instead of the one you want, and I think it doesn't even give the full test output.
Automated build processes are evil giant harnesses?
I never said evil. Just inappropriate for some tasks.
I've used lots of different build tools and installers over the years and MM strikes me as the only one that expected me to modify my source code to accommodate it.
It doesn't expect anything of the kind. If your script wasn't buggy in the first place, you wouldn't have to modify it.
In short, there are many ways to do things and many different environments that scripts run in. One should not assume that everyone who does something different than your way or MM's way is doing something evil and bad (technicaly speaking) the way you just did with me.
That's my point. You're assuming that it's M::B vs M::M, but it's not. The solution to your script being broken even in a M::B distro isn't to change M::M.