Re: Incompatibility between Test::Command and System::Command?
[email protected] (Buddy Burden)
| Newsgroups | perl.moose |
|---|---|
| Message-ID | <CAL0mxoT79JM6eckecOu9iiYSkx0rMbRvg_6f+7=+=AuzyPHbSg@mail.gmail.com> |
Grzegorz, > I've noticed the same thing, but with STDOUT and with Test::Output > and/or FastCGI. > > There is a hack in System::Command for Catalyst which causes this. > See https://rt.cpan.org/Public/Bug/Display.html?id=73614 Ah, good call on the RT ticket. I've added a comment there as well. I was hoping Philippe might weigh in, since I know he frequents the list. But, either way, it looks like it's not going to be fixed any time soon. I still don't understand _how_ it happens, though. I mean, I see which lines it is (I had worked that out earlier by selecting commenting/uncommenting), but I don't understand when System::Command::new is getting called. I suspect something in there is overriding core::system, but I can't actually find it. If that _is_ the case, though, I could theoretically restore the original core::system, couldn't I? Or, to ask what is perhaps a more list-relevant question: Does anyone know of a way to test for a directory being part of a Git working copy _other_ than by using Git::Repository? -- Buddy