>> Maybe I should just change it and take the flack if it breaks. What >> I'll do is run all the test suites I can that are available in a fully >> automated fashion and if none of those break I'll bite the bullet and do >> the putback and send out a heads-up that says people should be aware >> that some test suites could break. >> > > Yes, that's clearly the right thing to do. We don't even know for > certain that there is a test suite that will break; it's only rumored to > exist. Of course, if we ever ran across such a test, it would be trivial > to fix. >
I know for certain of some. I've filed 25 bugs against all known offenders, plus any suites that reference /.rhosts in their READMEs and any references that assume / that I could find. I hope this exercise will get the responsible parties to look closely at their suites and test the change. I am sure I missed some, but getting these fixed should make any ensuing breakage manageable. I've also taken responsibility for fixing the ssh control plane tool that many suites share. Fixing this should mitigate most of the issues I'd expect to encounter. -Paul
