Andreas J. Koenig wrote:
>>>>>> On Sat, 29 Dec 2007 20:18:17 -0600, Elliot Shank
galumph.com> said:> Note that this happened under
5.6.2. Under all my other perls it was a PASS.
Prior P::C releases have also failed in the same way in one of your 5.10 environments. The error messages about the locale are coming from aspell. I don't know what's different about your
5.8.x environments and why they succeed. I assume that you don't have multiple aspell installs. I'm guessing that the other's have different LANG* environment values. Having non C, non English locales is one of the reasons I really appreciate what you're doing.
> So the question remains, which Pod::Parser should you declare PREREQ.
However, we don't want to declare a Pod::Parser dependency. It's optional. The policy disables itself if it can't find any of the things it needs.
> Apparently Pod::Parser has a problem with my
5.6.2 and cannot be
> upgraded above 1.32. But when I try to step through the failing test,
> I get lost in forking and get no useful diagnostics. On cpantesters I
> see that Pod::Parser 1.34 has both PASS and FAIL with
5.6.2 but 1.35
> has only FAILs.
>
> Hrmm. I'm running out of wit and patience right now. Let me know if
> you find further facts that lead out of this maze:)
I don't believe that this is a Perl problem, per se. The specific problem here is related to the locale/aspell combination. We are not catching all possible ways that aspell can fail. (We do correctly deal with the absence of aspell.)
So, in general, I'm interested in the settings of the LANG* environment variables and aspell installs in the different environments you have. But regardless of those details, we need to get P::C's handling of the external process to be more bulletproof.
