On Thu, 16 Jun 2005, imacat wrote:
> I have forwarded this whole thread to Rob Janes, the current
> maintainer of CPANPLUS.
>
> Sorry first. Compress::Bzip2 won't generate reports
> when $Config{"cc"} is missing. So I assume there is some
> way to disable reports for missing $Config{"cc"}, and as a
> XS module author you should employ that. I was wrong.
> Digging into CPANPLUS I cannot found any mechanism for
> that. Maybe I was wrong here again.
>
> Personally I think whether $Config{"cc"} is available
> for XS modules should be checked at CPANPLUS, and a N/A
> report should be sent if $Config{"cc"} is not available.
> As a module author you can check if $Config{"cc"} is
> available and make some decision (although I don't know
> what decision). Maybe some graceful failure on that?
>
> And Randy, I don't agree with you. Perl may be
> distributed as binaries (and that is mostly the case).
> Often the building environment is not the same as the
> running environment. For the OS characteristics like
> $Config{"flock"}, it's reasonable to assume that it is
> reliable. But for $Config{"cc"}, assuming its existence
> is no doubt a mistake.
It seems to me that this issue should be decided at the
level of the Perl core, since this is responsible for
writing the glue for XS-based modules. If it was decided
that certain %Config entries should not be trusted, then it
would be more efficient to handle this at the core level,
rather than having every module author put in the same
checks.
--
best regards,
randy
