On Sun, Oct 31, 2004 at 08:26:54PM -0500, Ed Allen Smith wrote: > >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.
I don't think it can be usefully automated. Consider this simple sort of problem. if( eval { require Some::Module } ) { * one version of the code * } else { * some other version * } The code still works fine even without the module in question being there. > >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? No, you do not want Test::Smoke behaving differently from 'make test'. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/ Hokey religions and taking a nap are no match for a knife in the head. -- Black Mage http://www.nuklearpower.com/daily.php?date=040513