In message <[EMAIL PROTECTED]> (on 31 October 2004
20:13:43 -0500), [EMAIL PROTECTED] (Michael G Schwern) wrote:
>On Sun, Oct 31, 2004 at 02:18:23PM -0500, Ed Allen Smith wrote:
>> I note that some lib tests appear to require various extensions; for
>> instance, Unicode/Normalize is required for Unicode/Collate to pass its
>> tests (see http://www.nntp.perl.org/group/perl.daily-build.reports/22308,
>> for instance). Scanning modules for use/require and building a data file
>> (e.g., via Test::Prereq) for such prerequisites may be in order (if no data
>> file, assume no such prerequisites are present, and optionally rebuild it
>> later?).
>
>That would be centralizing internal details about individual modules, things
>that can change with every new version.
I had in mind centralizing it, as such, only in a way that could be
automatically constructed, if at all possible.
>The checks for unbuilt core modules are a special case that CPAN modules
>and authors don't normally have to do.
True. Perhaps something like the above should instead be part of
Test::Smoke, and the build process should simply have an option of "read
this file for tests to skip", which could have uses in other circumstances?
-Allen
--
Allen Smith http://cesario.rutgers.edu/easmith/
September 11, 2001 A Day That Shall Live In Infamy II
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." - Benjamin Franklin
